How severe is CVE-2026-63481?

No CVSS score has been assigned to CVE-2026-63481 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-63481?

CVE-2026-63481 affects the following packages: hurl (crates.io). Ecosystems affected: crates.io.

How do I fix CVE-2026-63481?

No patched version of hurl has shipped for CVE-2026-63481 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect CVE-2026-63481 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hurl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-63481 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2026-63481 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-63481 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-63481?

CVE-2026-63481 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 51th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-63481?

CVE-2026-63481 is classified as CWE-201 (CWE-201). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-63481 published, and has it been updated?

CVE-2026-63481 was published on August 20, 2026 and was last updated on October 21, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

CVE-2026-63481 — hurl

Fix: Orange-OpenSource/hurl@ed91c89

CVE-2026-63481 is a CWE-201 vulnerability in hurl. No vendor fix is recorded yet; mitigation options are listed below.

Hurl: Cookies in Cookies section leak when redirecting to a different host

Also known asGHSA-7w2g-9mf9-324m

Published

Aug 20, 2026

Updated

Oct 21, 2026

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-63481.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk+0.20%

Lower risk than most CVEs51th percentile — riskier than 51% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🦀hurl

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

The Bug

Hurl <= 8.0.1 lets you define cookies two ways in a .hurl file:

As a raw Cookie: header in the [Header]/headers area
In a dedicated [Cookies] section (parsed into RequestSpec.cookies)

When following a redirect to a different host, Hurl correctly strips security-sensitive data (Authorization, Cookie header, and basic-auth user) to avoid leaking credentials cross-host — mirroring libcurl's default behavior. But it only stripped the cookie that came in as a header. Cookies declared in the [Cookies] section were carried over to the new host unchanged — a credential-leak bug.

Hurl file that leaks cookies:

GET http://localhost:8000/follow-redirect-basic-auth?change_host=true
[Cookies]
fruit: lemon
HTTP 200

Hurl file that doesn't leak cookie:

GET http://localhost:8000/follow-redirect-basic-auth?change_host=true
Cookie: fruit=lemon
HTTP 200

Patch

With Hurl <= 8.0.1, user can use Cookie header instead of the dedicated [Cookies] section.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`hurl`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hurl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of hurl has shipped for CVE-2026-63481 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

## The Bug Hurl <= 8.0.1 lets you define cookies two ways in a .hurl file: 1. As a raw Cookie: header in the [Header]/headers area 2. In a dedicated [Cookies] section (parsed into RequestSpec.cookies) When following a redirect to a different host, Hurl correctly strips security-sensitive data (Authorization, Cookie header, and basic-auth user) to avoid leaking credentials cross-host — mirroring libcurl's default behavior. But it only stripped the cookie that came in as a header. Cookies declared in the [Cookies] section were carried over to the new host unchanged — a credential-leak bug.

O3 Security · Impact-Aware SCA

Is CVE-2026-63481 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works