# CVE-2025-52479: HTTP.jl vulnerable to CR/LF Injection in URIs

> Attackers can inject CR/LF characters into URIs, potentially leading to header injection or request smuggling if input is not validated.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jun 2025
- **Updated:** 7 May 2026
- **Also known as:** GHSA-4g68-4pxg-mw93, JLSEC-2025-1

## What is CVE-2025-52479?

CVE-2025-52479 is a high-severity vulnerability in JuliaWeb HTTP.jl, published on 25 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HTTP.jl provides HTTP client and server functionality for Julia, and URIs.jl parses and works with Uniform Resource Identifiers (URIs). URIs.jl prior to version 1.6.0 and HTTP.jl prior to version 1.10.17 allows the construction of URIs containing CR/LF characters. If user input was not otherwise escaped or protected, this can lead to a CRLF injection attack. Users of HTTP.jl should upgrade immediately to HTTP.jl v1.10.17, and users of URIs.jl should upgrade immediately to URIs.jl v1.6.0. The check for valid URIs is now in the URI.jl package, and the latest version of HTTP.jl incorporates that fix. As a workaround, manually validate any URIs before passing them on to functions in this package.

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

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


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

Upgrade to a fixed version.

## Is CVE-2025-52479 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52479 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-52479 is a high-severity vulnerability in JuliaWeb HTTP.jl, published on 25 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52479 exists.

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-52479/ (Markdown: https://insights.sbomify.com/CVE-2025-52479/index.md)
```

## Sources

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

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