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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-63481: 0.66% estimated exploitation activity in the next 30 days; percentile 51.77 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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. Hurl file that leaks cookies: Hurl file that doesn't leak cookie: Patch With Hurl <= 8.0.1, user can use Cookie header instead of the dedicated [Cookies] section.

Published by the source

2 Sep 2026, 22:11 UTC

Last modified by the source

2 Sep 2026, 22:15 UTC

Source last checked

26 Oct 2026, 15:43 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-7w2g-9mf9-324m

2. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-7w2g-9mf9-324m

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-63481

Advisory: Hurl: Cookies in Cookies section leak when redirecting to a different host
IDs: CVE-2026-63481, GHSA-7w2g-9mf9-324m
Record: https://patchnext.com/advisories/cve-2026-63481 (revision 3, source checked 26 Oct 2026, 15:43 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io hurl: affected <= 8.0.1

## Suggested inspection (read-only)
- crates.io hurl: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on hurl.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-7w2g-9mf9-324m (OSV record GHSA-7w2g-9mf9-324m lists affected ranges: crates.io hurl >=0 <=8.0.1)
- Verified: https://github.com/advisories/GHSA-7w2g-9mf9-324m (GitHub-reviewed advisory GHSA-7w2g-9mf9-324m lists affected ranges: crates.io hurl >=0 <=8.0.1)

Commands are suggestions: review each one before running it.