CVE-2026-9546

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-03. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this weekElevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

A vulnerability in libcurl caused the HTTP Referer: header to persist even when explicitly cleared. While the documentation states that passing NULL to CURLOPT_REFERER suppresses the header, the option failed to clear the internal state. As a result the previous referrer string was erroneously reused and sent in subsequent requests, potentially leaking sensitive information to unintended servers.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
EPSS
47.4%
KEV
Not listed

Published

July 3, 2026

Last Modified

July 7, 2026

Advisory Details (3)

Auto-updated Jul 7, 2026
No patch confirmed yet.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrust-main-1.96.1-1.hum12026-07-02redhat
redhatcurl-main-8.21.0-0.1.hum12026-06-24redhat

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.

Data Freshness Timeline

(refreshed 14× 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.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:25 UTCEPSS rescore
  3. 2026-07-21 15:25 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-17 06:29 UTCVendor advisory
  9. 2026-07-17 06:29 UTCGHSA enrichment
  10. 2026-07-16 18:58 UTCVendor advisory
  11. 2026-07-16 18:58 UTCGHSA enrichment
  12. 2026-07-16 17:03 UTCEPSS rescore
  13. 2026-07-16 07:26 UTCVendor advisory
  14. 2026-07-16 07:26 UTCGHSA enrichment
  15. 2026-07-15 19:54 UTCVendor advisory
  16. 2026-07-15 19:54 UTCGHSA enrichment
  17. 2026-07-15 16:57 UTCEPSS rescore
  18. 2026-07-15 08:23 UTCVendor advisory
  19. 2026-07-15 08:22 UTCGHSA enrichment
  20. 2026-07-15 02:00 UTCEPSS rescore
  21. 2026-07-14 20:50 UTCVendor advisory
  22. 2026-07-14 20:50 UTCGHSA enrichment
  23. 2026-07-14 09:18 UTCVendor advisory
  24. 2026-07-14 09:18 UTCGHSA enrichment
  25. 2026-07-13 22:31 UTCEPSS rescore
Show 33 more
  1. 2026-07-13 21:45 UTCVendor advisory
  2. 2026-07-13 21:45 UTCGHSA enrichment
  3. 2026-07-13 10:13 UTCVendor advisory
  4. 2026-07-13 10:12 UTCGHSA enrichment
  5. 2026-07-13 06:13 UTCEPSS rescore
  6. 2026-07-12 22:40 UTCVendor advisory
  7. 2026-07-12 22:40 UTCGHSA enrichment
  8. 2026-07-12 11:08 UTCVendor advisory
  9. 2026-07-12 11:07 UTCGHSA enrichment
  10. 2026-07-12 05:46 UTCEPSS rescore
  11. 2026-07-11 23:35 UTCVendor advisory
  12. 2026-07-11 23:35 UTCGHSA enrichment
  13. 2026-07-11 12:02 UTCVendor advisory
  14. 2026-07-11 12:02 UTCGHSA enrichment
  15. 2026-07-11 08:27 UTCEPSS rescore
  16. 2026-07-11 00:30 UTCVendor advisory
  17. 2026-07-11 00:30 UTCGHSA enrichment
  18. 2026-07-10 12:59 UTCVendor advisory
  19. 2026-07-10 12:58 UTCGHSA enrichment
  20. 2026-07-10 01:26 UTCVendor advisory
  21. 2026-07-10 01:26 UTCGHSA enrichment
  22. 2026-07-09 19:10 UTCEPSS rescore
  23. 2026-07-09 13:51 UTCEG score recompute 7.50
  24. 2026-07-09 13:51 UTCVendor advisory
  25. 2026-07-09 13:51 UTCGHSA enrichment
  26. 2026-07-08 15:16 UTCEPSS rescore
  27. 2026-07-07 13:46 UTCEPSS rescore
  28. 2026-07-06 17:36 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  29. 2026-07-06 16:27 UTCEPSS rescore
  30. 2026-07-06 11:10 UTCGHSA enrichment
  31. 2026-07-05 02:31 UTCEPSS rescore
  32. 2026-07-03 08:27 UTCEG score recompute
  33. 2026-07-03 08:26 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-9546?
CVE-2026-9546 is a high vulnerability published on July 3, 2026. A vulnerability in libcurl caused the HTTP Referer: header to persist even when explicitly cleared. While the documentation states that passing NULL to CURLOPT_REFERER suppresses the header, the option failed to clear the internal state. As a result the previous referrer string was erroneously…
When was CVE-2026-9546 disclosed?
CVE-2026-9546 was first published in the National Vulnerability Database on July 3, 2026, with the most recent update on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9546 actively exploited?
CVE-2026-9546 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 47.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-9546?
CVE-2026-9546 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-9546?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9546, 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

Explore the affected products and dependency analysis for CVE-2026-9546

Explore →

Is Your Infrastructure Affected by CVE-2026-9546?

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