What is CVE-2026-63481?

CVE-2026-63481 is a medium-severity security vulnerability in hurl (rust), affecting versions <= 8.0.1. No fixed version is listed yet.

Which versions of hurl are affected by CVE-2026-63481?

hurl (rust) versions <= 8.0.1 is affected.

Is there a fix for CVE-2026-63481?

No fixed version is listed for CVE-2026-63481 yet. Monitor the advisory for updates and apply mitigations in the interim.

Is CVE-2026-63481 exploitable, and should I be worried?

Whether CVE-2026-63481 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-63481 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-63481 in hurl

Q: Which versions of hurl are affected by CVE-2026-63481?

hurl (rust) versions <= 8.0.1 is affected.

Q: Is there a fix for CVE-2026-63481?

No fixed version is listed for CVE-2026-63481 yet. Monitor the advisory for updates and apply mitigations in the interim.

Q: Is CVE-2026-63481 exploitable, and should I be worried?

Whether CVE-2026-63481 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-63481 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Summary

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

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

Impact

Affected versions

hurl (<= 8.0.1)

Security releases

Not available

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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

Frequently Asked Questions

What is CVE-2026-63481? CVE-2026-63481 is a medium-severity security vulnerability in hurl (rust), affecting versions <= 8.0.1. No fixed version is listed yet.
Which versions of hurl are affected by CVE-2026-63481? hurl (rust) versions <= 8.0.1 is affected.
Is there a fix for CVE-2026-63481? No fixed version is listed for CVE-2026-63481 yet. Monitor the advisory for updates and apply mitigations in the interim.
Is CVE-2026-63481 exploitable, and should I be worried? Whether CVE-2026-63481 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-63481 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.