Menu

Star on GitHub · 3.2k

CVE-2026-9546

7.5 · HIGH

A vulnerability in libcurl caused the HTTP `Referer:` header to persist even when explicitly cleared.

Published Jul 3, 2026EPSS 0.65%

Overview

CVE-2026-9546 is a high-severity vulnerability. It was published on July 3, 2026 and has a CVSS 3.1 base score of 7.5 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-9546?

CVE-2026-9546 is a high-severity vulnerability. It was published on July 3, 2026 and has a CVSS 3.1 base score of 7.5 (HIGH).

How severe is CVE-2026-9546?

This vulnerability has a CVSS 3.1 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2026-9546?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-9546?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-9546 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all