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
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 7.5Exploit: None knownExposed services: Not assessed

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.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

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%
EPSS PROB
0.8%
EPSS %ILE
55th
KEV
Not listed

Published

May 7, 2026

Last Modified

September 18, 2026

Advisory Details (4)

Auto-updated May 12, 2026
Patch available.
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 / EcosystemFix (by version range) / PatchReleasedSource
redhatgit-lfs-0:3.6.1-2.el9_6.72026-09-14redhat
redhatgit-lfs-0:3.6.1-2.el10_0.72026-09-14redhat
redhatgit-lfs-0:3.2.0-2.el9_2.102026-09-14redhat
redhatoadp/oadp-velero-rhel9:17888604612026-09-09redhat
redhatimage-builder-0:52.1-1.el9_8.22026-09-09redhat
redhatrhoai/odh-trustyai-service-operator-rhel9:17873300732026-09-08redhat
redhatimage-builder-0:52.1-1.el10_2.22026-09-08redhat
redhatopenshift4/ose-ansible-rhel9-operator:17875543472026-09-03redhat
redhatose-gcp-gcr-image-credential-provider-0:4.17.0-202608122146.p2.g8ce997d.assembly.stream.el82026-09-03redhat
redhatgolang-0:1.26.5-1.el9_22026-08-31redhat
redhatrhc-1:0.3.2-6.el10_02026-08-31redhat
redhatrhoai/odh-workload-variant-autoscaler-controller-rhel9:17875622002026-08-27redhat
redhatopenshift4/ose-sdn-rhel8:17870028072026-08-26redhat
redhatopenshift4/ose-ansible-rhel9-operator:17867544252026-08-26redhat
redhatrhoso-operators/sg-core-rhel9:17866126622026-08-26redhat
redhatose-gcp-gcr-image-credential-provider-0:4.16.0-202608111505.p2.g26b43df.assembly.stream.el82026-08-26redhat
redhatopenshift4/ose-sdn-rhel9:17870551352026-08-26redhat
redhatopenshift4/ose-ansible-operator:17870018632026-08-26redhat
redhatose-gcp-gcr-image-credential-provider-0:4.18.0-202608121933.p2.g6ea2356.assembly.stream.el82026-08-26redhat
redhatopenshift4/ose-ansible-operator:17870280972026-08-26redhat
redhatose-aws-ecr-image-credential-provider-0:4.14.0-202608131802.p2.g9a7820e.assembly.stream.el82026-08-26redhat
redhatopenshift4/ose-ansible-rhel9-operator:17867883312026-08-26redhat
redhatose-gcp-gcr-image-credential-provider-0:4.15.0-202608131733.p2.gfc50272.assembly.stream.el82026-08-26redhat
redhatmulticluster-engine/discovery-rhel9:17866585192026-08-25redhat
redhatoadp/oadp-velero-rhel9:17869445402026-08-25redhat
redhatgolang-0:1.26.5-1.el9_42026-08-20redhat
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
redhatmulticluster-engine/work-rhel9:17869072762026-08-19redhat

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 rangeFix by version rangeDependents
golang-1.251.25.0-1 ... 1.25.9-1 (11 versions)
  • every version up to 1.25.10-1: fixed in 1.25.10-1
—
golang-1.261.26.0-1 ... 1.26~rc3-2 (9 versions)
  • every version up to 1.26.3-1: fixed in 1.26.3-1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
golang-1.151.15.15-1 ... 1.15.9-6 (10 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
golang-1.191.19.10-1 ... 1.19.9-1 (12 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
golang-1.241.24.12-1 ... 1.24.9-1 (10 versions)
  • every version on: no fix on record
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
stdlib—
  • every version up to 1.25.10: fixed in 1.25.10
  • 1.26.0-0 up to 1.26.3: fixed in 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 4× in last 7d / 58× 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 431 total refreshes for this CVE.

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

Related CVEs(same product + 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 on May 7, 2026, with the most recent update on September 18, 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 0.8% probability of exploitation in the next 30 days (55th percentile of EPSS-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?
A fix for CVE-2026-33811 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-33811 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs