CVE-2026-33811

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-07. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — Patch released this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

When using LookupCNAME with the cgo DNS resolver, a very long CNAME response can trigger a double-free of C memory and a crash.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
54%
KEV
Not listed

Published

May 7, 2026

Last Modified

August 20, 2026

Advisory Details (4)

Auto-updated May 12, 2026
No patch confirmed yet.
generic

GO-2026-4981 - Go Packages

https://pkg.go.dev/vuln/GO-2026-4981
generic
https://groups.google.com/g/golang-announce/c/qcCIEXso47M
generic

net: double-free of cgo pointer when handling long CNAME response · Issue #78803 · golang/go · GitHub

https://go.dev/issue/78803
generic
https://go.dev/cl/767860

Vendor Advisories for CVE-2026-33811(20)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhacm2/klusterlet-addon-controller-rhel9:17869083012026-08-19redhat
redhatose-aws-ecr-image-credential-provider-0:4.19.0-202608111604.p2.g425c1c5.assembly.stream.el92026-08-19redhat
redhatopenshift4/ose-ansible-rhel9-operator:17864907452026-08-19redhat
redhatopenshift4/ose-ansible-rhel9-operator:17865261392026-08-18redhat
redhatopenshift-logging/logging-loki-rhel9:17866452482026-08-18redhat
redhatopenshift4/ose-ansible-rhel9-operator:17865258402026-08-18redhat
redhatopenshift4/ose-hypershift-rhel9:17865730752026-08-18redhat
redhatcompliance/openshift-compliance-operator-bundle:17863800822026-08-13redhat
redhatetcd-0:3.3.23-22.el8ost2026-08-13redhat
redhatrhc-worker-playbook-0:0.2.3-6.el10_02026-08-12redhat
redhatworkload-availability/self-node-remediation-rhel9-operator:17852030362026-08-12redhat
redhatworkload-availability/storage-based-remediation-rhel9-operator:17852034742026-08-12redhat
redhatworkload-availability/node-healthcheck-rhel9-operator:17852027232026-08-12redhat
redhatworkload-availability/fence-agents-remediation-rhel9-operator:17852030792026-08-12redhat
redhatworkload-availability/machine-deletion-remediation-rhel9-operator:17852035082026-08-12redhat
redhatgolang-github-danielqsj-kafka_exporter2026-08-12redhat
redhatworkload-availability/node-maintenance-rhel9-operator:17852028472026-08-12redhat
redhatrhc-worker-script-0:0.11-1.el7_92026-08-12redhat
redhatrh-lightspeed-runtimes/runtimes-inventory-rhel9-operator:17864837822026-08-12redhat
redhatopentelemetry-collector-0:0.152.1-1.el10_02026-08-11redhat
redhatopentelemetry-collector-0:0.152.1-1.el9_42026-08-11redhat
redhatmulticluster-globalhub/multicluster-globalhub-agent-rhel9:17857759482026-08-11redhat
redhatopentelemetry-collector-0:0.152.1-1.el9_62026-08-11redhat
redhatsatellite/iop-vmaas-rhel9:17859299942026-08-06redhat
redhatoadp/oadp-velero-rhel9:17851808782026-08-06redhat
redhatsource-to-image/source-to-image-rhel9:17847280362026-08-06redhat
redhatsatellite/iop-vmaas-rhel9:17859233082026-08-06redhat
redhatyggdrasil-0:0.4.7-5.el10_02026-08-06redhat
redhatopenshift-logging/eventrouter-rhel9:17854188512026-08-05redhat
redhatconforma-cli-stack-v1-4-1.4.32026-08-05redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 5 ecosystems)
Debian:14(2)
PackageVulnerable rangeFixed inDependents
golang-1.251.25.0-1 ... 1.25.9-1 (11 versions)1.25.10-1—
golang-1.261.26.0-1 ... 1.26~rc3-2 (9 versions)1.26.3-1—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
golang-1.151.15.15-1 ... 1.15.9-6 (10 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
golang-1.191.19.10-1 ... 1.19.9-1 (12 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
golang-1.241.24.12-1 ... 1.24.9-1 (10 versions)——
Go(1)
PackageVulnerable rangeFixed inDependents
stdlib—1.26.3—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 30× in last 7d / 162× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 306 total refreshes for this CVE.

  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 22:55 UTCEPSS rescore
  3. 2026-08-20 13:58 UTCVendor advisory
  4. 2026-08-20 13:58 UTCGHSA enrichment
  5. 2026-08-20 12:43 UTCEG score recompute
  6. 2026-08-20 12:43 UTCVendor advisory
  7. 2026-08-20 12:43 UTCGHSA enrichment
  8. 2026-08-19 17:03 UTCEPSS rescore
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-18 12:19 UTCEG score recompute
  11. 2026-08-18 12:19 UTCVendor advisory
  12. 2026-08-18 12:18 UTCGHSA enrichment
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 12:20 UTCVendor advisory
  15. 2026-08-17 12:20 UTCGHSA enrichment
  16. 2026-08-17 12:12 UTCEG score recompute
  17. 2026-08-17 12:12 UTCVendor advisory
  18. 2026-08-17 12:12 UTCGHSA enrichment
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 04:43 UTCEG score recompute
  21. 2026-08-16 04:43 UTCVendor advisory
  22. 2026-08-16 04:43 UTCGHSA enrichment
  23. 2026-08-16 02:14 UTCEPSS rescore
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-15 00:53 UTCVendor advisory
Show 75 more
  1. 2026-08-15 00:53 UTCGHSA enrichment
  2. 2026-08-14 13:27 UTCVendor advisory
  3. 2026-08-14 13:27 UTCGHSA enrichment
  4. 2026-08-14 12:29 UTCVendor advisory
  5. 2026-08-14 12:29 UTCGHSA enrichment
  6. 2026-08-14 03:18 UTCEG score recompute
  7. 2026-08-14 03:18 UTCVendor advisory
  8. 2026-08-14 03:18 UTCGHSA enrichment
  9. 2026-08-13 22:00 UTCEPSS rescore
  10. 2026-08-13 13:38 UTCVendor advisory
  11. 2026-08-13 13:38 UTCGHSA enrichment
  12. 2026-08-13 12:28 UTCVendor advisory
  13. 2026-08-13 12:28 UTCGHSA enrichment
  14. 2026-08-13 00:03 UTCEG score recompute
  15. 2026-08-13 00:03 UTCVendor advisory
  16. 2026-08-13 00:03 UTCGHSA enrichment
  17. 2026-08-12 13:50 UTCEPSS rescore
  18. 2026-08-12 12:38 UTCVendor advisory
  19. 2026-08-12 12:38 UTCGHSA enrichment
  20. 2026-08-12 12:12 UTCVendor advisory
  21. 2026-08-12 12:12 UTCGHSA enrichment
  22. 2026-08-12 00:49 UTCEG score recompute
  23. 2026-08-12 00:49 UTCVendor advisory
  24. 2026-08-12 00:49 UTCGHSA enrichment
  25. 2026-08-11 13:23 UTCVendor advisory
  26. 2026-08-11 13:23 UTCGHSA enrichment
  27. 2026-08-11 12:24 UTCVendor advisory
  28. 2026-08-11 12:24 UTCGHSA enrichment
  29. 2026-08-11 01:24 UTCEG score recompute
  30. 2026-08-11 01:24 UTCVendor advisory
  31. 2026-08-11 01:24 UTCGHSA enrichment
  32. 2026-08-11 00:00 UTCEPSS rescore
  33. 2026-08-10 13:21 UTCVendor advisory
  34. 2026-08-10 13:21 UTCGHSA enrichment
  35. 2026-08-10 12:26 UTCVendor advisory
  36. 2026-08-10 12:26 UTCGHSA enrichment
  37. 2026-08-10 01:20 UTCVendor advisory
  38. 2026-08-10 01:20 UTCGHSA enrichment
  39. 2026-08-09 13:55 UTCEG score recompute
  40. 2026-08-09 13:55 UTCVendor advisory
  41. 2026-08-09 13:54 UTCGHSA enrichment
  42. 2026-08-09 13:46 UTCEPSS rescore
  43. 2026-08-09 02:29 UTCEG score recompute
  44. 2026-08-09 02:29 UTCVendor advisory
  45. 2026-08-09 02:29 UTCGHSA enrichment
  46. 2026-08-08 16:37 UTCEPSS rescore
  47. 2026-08-08 11:17 UTCVendor advisory
  48. 2026-08-08 11:17 UTCGHSA enrichment
  49. 2026-08-07 23:51 UTCEG score recompute
  50. 2026-08-07 23:51 UTCVendor advisory
  51. 2026-08-07 23:51 UTCGHSA enrichment
  52. 2026-08-07 12:25 UTCVendor advisory
  53. 2026-08-07 12:25 UTCGHSA enrichment
  54. 2026-08-07 12:09 UTCVendor advisory
  55. 2026-08-07 12:09 UTCGHSA enrichment
  56. 2026-08-07 01:48 UTCEG score recompute
  57. 2026-08-07 01:48 UTCVendor advisory
  58. 2026-08-07 01:48 UTCGHSA enrichment
  59. 2026-08-06 13:46 UTCEPSS rescore
  60. 2026-08-06 13:39 UTCVendor advisory
  61. 2026-08-06 13:39 UTCGHSA enrichment
  62. 2026-08-06 12:34 UTCVendor advisory
  63. 2026-08-06 12:34 UTCGHSA enrichment
  64. 2026-08-06 01:15 UTCEG score recompute
  65. 2026-08-06 01:15 UTCVendor advisory
  66. 2026-08-06 01:15 UTCGHSA enrichment
  67. 2026-08-05 19:17 UTCEPSS rescore
  68. 2026-08-05 13:50 UTCVendor advisory
  69. 2026-08-05 13:50 UTCGHSA enrichment
  70. 2026-08-05 12:34 UTCEG score recompute
  71. 2026-08-05 12:34 UTCVendor advisory
  72. 2026-08-05 12:33 UTCGHSA enrichment
  73. 2026-08-04 15:10 UTCEPSS rescore
  74. 2026-08-04 13:26 UTCVendor advisory
  75. 2026-08-04 13:26 UTCGHSA enrichment

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-33811?
CVE-2026-33811 is a high vulnerability published on May 7, 2026. When using LookupCNAME with the cgo DNS resolver, a very long CNAME response can trigger a double-free of C memory and a crash.
When was CVE-2026-33811 disclosed?
CVE-2026-33811 was first published in the National Vulnerability Database on May 7, 2026, with the most recent update on August 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-33811 actively exploited?
CVE-2026-33811 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 45.8% of all scored CVEs.
What is the CVSS score of CVE-2026-33811?
CVE-2026-33811 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-33811?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33811, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-33811

Explore →

Is Your Infrastructure Affected by CVE-2026-33811?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs