CVE Tools

CVE-2026-97054

HTTP/1 server crash due to MaxBytesReader header race in net/http

CVE-2026-97054 is a race condition in Go standard library net/http (CVSS 5.9, Medium).

No known exploitation. EPSS puts it in the 33rd percentile. Fixed versions are out.

Check it yourself

OpenVAS · 12 checks

e.g. OID 1.3.6.1.4.1.25623.1.1.18.1.2026.12529.1

Run the check

Published Updated Sources: CVE.org, NVD

What to do

Find your product and version, then upgrade to the build on the right.

  • Go standard library net/httpAffected: < 1.26.11Upgrade to: 1.26.11Affected: ≥ 1.27.0-0, < 1.27.4Upgrade to: 1.27.4Stated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

For HTTP/1 servers, when MaxBytesReader's limit is exceeded, "Connection: close" header is automatically set without synchronization, which might race with another header being set explicitly in the server handler. As a result, an HTTP/1 server that utilizes MaxBytesReader or MaxBytesHandler can crash due to runtime panic if its handler reads the request body concurrently with writing the response header.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS33rd
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.4% chance of exploitation activity in the next 30 days, which ranks it in the 33rd percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

7 events over 8 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. Record updated
  3. Record updated
  4. Publishedweakness classified, att&ck mapped, record updated

Affected products

Technical detail

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Scored 5.9 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality NoneNo confidentiality impact
  • Integrity NoneNo integrity impact
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Questions about CVE-2026-97054

Is CVE-2026-97054 being exploited?
No exploitation is confirmed and no public exploit is known. EPSS puts the chance of exploitation in the next 30 days at 0.4%.
Which versions are affected by CVE-2026-97054?
Net/http: < 1.26.11; ≥ 1.27.0-0, < 1.27.4.
How do I fix or mitigate CVE-2026-97054?
Upgrade to a fixed build for your product branch: 1.26.11, 1.27.4.

Last updated

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Net/http, not every advisory.