CVE Tools

CVE-2026-46600

Parsing an invalid SVCB or HTTPS RR can panic in golang.org/x/net/dns/dnsmessage

CVE-2026-46600 is an out-of-bounds read in Go standard library net (CVSS 7.5, High).

No known exploitation. EPSS puts it in the 47th percentile. Fixed versions are out.

Check it yourself

OpenVAS · 17 checks

e.g. OID 1.3.6.1.4.1.25623.1.1.10.2026.0341

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 netAffected: ≥ 1.26.0-0, < 1.26.6Upgrade to: 1.26.6Affected: ≥ 1.27.0-0, < 1.27.0-rc.3Upgrade to: 1.27.0-rc.3Stated by: CVE record
  • Golang.org/x/net/dns/dnsmessageAffected: < 0.56.0Upgrade to: 0.56.0Stated by: CVE record

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

What it is

From the CVE record

Parsing an invalid SVCB or HTTPS RR can panic when the size of a parameter value overflows the message buffer.

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.

EPSS47th
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.5% chance of exploitation activity in the next 30 days, which ranks it in the 47th percentile of scored CVEs.

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

Lifecycle

9 events over 95 days, from the signal feeds we watch.

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

Affected products

Technical detail

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

Scored 7.5 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • 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-46600

Is CVE-2026-46600 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.5%.
Which versions are affected by CVE-2026-46600?
Net: ≥ 1.26.0-0, < 1.26.6; ≥ 1.27.0-0, < 1.27.0-rc.3. Golang.org/x/net/dns/dnsmessage: < 0.56.0.
How do I fix or mitigate CVE-2026-46600?
Upgrade to a fixed build for your product branch: 1.26.6, 1.27.0-rc.3, 0.56.0.

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, not every advisory.