Is stdlib affected by CVE-2026-33811?

Go stdlib is affected in =1.26.0-0 <1.26.3.

Is CVE-2026-33811 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.5%.

medium

CVE-2026-33811

Q: Is CVE-2026-33811 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.5%.

Go · stdlib

Summary

Crash when handling long CNAME response in net

Severity: medium
EPSS: 0.5% (p39)
Also known as: BIT-golang-2026-33811, GO-2026-4981
Published: 2026-05-07

References

https://go.dev/issue/78803
https://go.dev/cl/767860
https://groups.google.com/g/golang-announce/c/qcCIEXso47M

Related advisories

CVE-2026-27145 — medium · Go/stdlib
CVE-2026-42504 — medium · Go/stdlib
CVE-2026-42507 — medium · Go/stdlib
CVE-2026-39820 — medium · Go/stdlib
CVE-2026-33814 — medium · Go/stdlib
CVE-2026-39826 — medium · Go/stdlib
CVE-2026-42499 — medium · Go/stdlib
CVE-2026-39823 — medium · Go/stdlib

Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.

Check my repo

Summarize with AI

ChatGPT Claude Perplexity

Sources: CISA KEV (public domain), OSV.dev & GitHub Advisory Database (CC-BY-4.0), FIRST EPSS, NVD/CWE (public domain). Served live from the Stateward advisory database.