# CVE-2025-61689: HTTP.jl vulnerable to Header injection/Response splitting via header construction.


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 10 Oct 2025
- **Updated:** 10 Oct 2025
- **Also known as:** GHSA-h3x8-ppwj-6vcj, JLSEC-2025-40

## What is CVE-2025-61689?

CVE-2025-61689 is a high-severity vulnerability in JuliaWeb HTTP.jl, published on 10 Oct 2025. 

### Official description

HTTP.jl is an HTTP client and server functionality for the Julia programming language. Prior to version 1.10.19, HTTP.jl did not validate header names/values for illegal characters, allowing CRLF-based header injection and response splitting. This enables HTTP response splitting and header injection, leading to cache poisoning, XSS, session fixation, and more. This issue is fixed in HTTP.jl  `v1.10.19`.

Weakness: CWE-113 (Improper Neutralization of CRLF Sequences in HTTP Headers)

## Which versions are affected by CVE-2025-61689?


## How do I fix CVE-2025-61689?

Upgrade to a fixed version.

## Is CVE-2025-61689 being exploited?

There is no known exploitation of CVE-2025-61689 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-61689 and fix it if it is affected.

What it is: CVE-2025-61689 is a high-severity vulnerability in JuliaWeb HTTP.jl, published on 10 Oct 2025. 
Exploitation: There is no known exploitation of CVE-2025-61689 in the wild and no public exploit code.

Affected product: JuliaWeb HTTP.jl. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-61689/ (Markdown: https://insights.sbomify.com/CVE-2025-61689/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-61689
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-61689
- OSV: https://osv.dev/vulnerability/CVE-2025-61689

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-61689/
Summaries are generated and may contain mistakes; the official description above is the record.