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.
CVE-2026-9546
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.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 65(Attend)EG Risk 65/100SSVC: Attend
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 computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 33%
- KEV
- Not listed
Published
July 3, 2026
Last Modified
July 7, 2026
Advisory Details (3)
Auto-updated Jul 7, 2026Vendor Advisories for CVE-2026-9546(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- GHSA-25rx-86v8-32c6GitHub Security AdvisoriesHigh
A vulnerability in libcurl caused the HTTP `Referer:` header to persist even when explicitly...
- RHSA-2026:34975Red Hat Product SecurityCritical
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
- RHSA-2026:29017Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
Patch Availability(2)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | rust-main-1.96.1-1.hum1 | 2026-07-02 | redhat |
| redhat | curl-main-8.21.0-0.1.hum1 | 2026-06-24 | redhat |
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
(2 across 2 ecosystems)
Alpine:v3.24(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| curl | — | 8.21.0-r0 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| curl | 8.14.1-2 ... 8.21.0~rc1-1+exp1 (59 versions) | 8.21.0~rc2-1 | — |
Data Freshness Timeline
(refreshed 42× 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 219 total refreshes for this CVE.
- 2026-08-21 04:26 UTCEG score recompute
- 2026-08-21 04:26 UTCVendor advisory
- 2026-08-21 04:26 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 15:52 UTCVendor advisory
- 2026-08-20 15:52 UTCGHSA enrichment
- 2026-08-20 03:56 UTCEG score recompute
- 2026-08-20 03:56 UTCVendor advisory
- 2026-08-20 03:56 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 10:52 UTCVendor advisory
- 2026-08-19 10:52 UTCGHSA enrichment
- 2026-08-18 23:21 UTCEG score recompute
- 2026-08-18 23:21 UTCVendor advisory
- 2026-08-18 23:21 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 11:46 UTCVendor advisory
- 2026-08-18 11:46 UTCGHSA enrichment
- 2026-08-17 22:49 UTCEG score recompute
- 2026-08-17 22:49 UTCVendor advisory
- 2026-08-17 22:49 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 07:51 UTCVendor advisory
- 2026-08-17 07:51 UTCGHSA enrichment
- 2026-08-16 20:19 UTCEG score recompute
Show 75 moreShow fewer
- 2026-08-16 20:19 UTCVendor advisory
- 2026-08-16 20:19 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 08:47 UTCEG score recompute
- 2026-08-16 08:47 UTCVendor advisory
- 2026-08-16 08:47 UTCGHSA enrichment
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 21:16 UTCVendor advisory
- 2026-08-15 21:16 UTCGHSA enrichment
- 2026-08-15 09:44 UTCEG score recompute
- 2026-08-15 09:44 UTCVendor advisory
- 2026-08-15 09:44 UTCGHSA enrichment
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 22:12 UTCVendor advisory
- 2026-08-14 22:12 UTCGHSA enrichment
- 2026-08-14 10:41 UTCVendor advisory
- 2026-08-14 10:41 UTCGHSA enrichment
- 2026-08-13 23:09 UTCEG score recompute
- 2026-08-13 23:09 UTCVendor advisory
- 2026-08-13 23:09 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 11:37 UTCVendor advisory
- 2026-08-13 11:37 UTCGHSA enrichment
- 2026-08-13 00:05 UTCEG score recompute
- 2026-08-13 00:05 UTCVendor advisory
- 2026-08-13 00:05 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 12:34 UTCVendor advisory
- 2026-08-12 12:34 UTCGHSA enrichment
- 2026-08-12 01:02 UTCEG score recompute
- 2026-08-12 01:02 UTCVendor advisory
- 2026-08-12 01:02 UTCGHSA enrichment
- 2026-08-11 13:43 UTCEPSS rescore
- 2026-08-11 13:31 UTCVendor advisory
- 2026-08-11 13:31 UTCGHSA enrichment
- 2026-08-11 01:59 UTCEG score recompute
- 2026-08-11 01:59 UTCVendor advisory
- 2026-08-11 01:59 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 14:28 UTCVendor advisory
- 2026-08-10 14:28 UTCGHSA enrichment
- 2026-08-10 02:57 UTCVendor advisory
- 2026-08-10 02:57 UTCGHSA enrichment
- 2026-08-09 15:25 UTCEG score recompute
- 2026-08-09 15:25 UTCVendor advisory
- 2026-08-09 15:25 UTCGHSA enrichment
- 2026-08-09 13:47 UTCEPSS rescore
- 2026-08-09 03:54 UTCEG score recompute
- 2026-08-09 03:54 UTCVendor advisory
- 2026-08-09 03:54 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 16:23 UTCVendor advisory
- 2026-08-08 16:23 UTCGHSA enrichment
- 2026-08-08 04:51 UTCVendor advisory
- 2026-08-08 04:51 UTCGHSA enrichment
- 2026-08-07 17:20 UTCEG score recompute
- 2026-08-07 17:20 UTCVendor advisory
- 2026-08-07 17:20 UTCGHSA enrichment
- 2026-08-07 16:30 UTCEPSS rescore
- 2026-08-07 05:48 UTCVendor advisory
- 2026-08-07 05:48 UTCGHSA enrichment
- 2026-08-06 18:16 UTCEG score recompute
- 2026-08-06 18:16 UTCVendor advisory
- 2026-08-06 18:16 UTCGHSA enrichment
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 06:45 UTCEG score recompute
- 2026-08-06 06:45 UTCVendor advisory
- 2026-08-06 06:45 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 19:13 UTCVendor advisory
- 2026-08-05 19:13 UTCGHSA enrichment
- 2026-08-05 07:41 UTCVendor advisory
- 2026-08-05 07:41 UTCGHSA enrichment
- 2026-08-04 20:08 UTCEG score recompute
- 2026-08-04 20:08 UTCVendor advisory
Related CVEs(same vendor)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-1009EG 10.0EPSS p93HIGH
- CVE-2001-0554EG 10.0EPSS p98HIGH
- CVE-2001-1162EG 10.0EPSS p96HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
Frequently asked(5)
What is CVE-2026-9546?
When was CVE-2026-9546 disclosed?
Is CVE-2026-9546 actively exploited?
What is the CVSS score of CVE-2026-9546?
How do I remediate CVE-2026-9546?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-9546
Is Your Infrastructure Affected by CVE-2026-9546?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.