Vulnerability in guzzle (UBUNTU-CVE-2026-67354)
Summary
Vulnerability in guzzle (UBUNTU-CVE-2026-67354). Confidential information can be exposed externally. Exploitable via Referer header. Mitigation: upgrade to 7.15.1 or later.
Original description
The description as published by the source.
guzzlehttp/guzzle versions before 7.15.1 contain an information disclosure vulnerability in RedirectMiddleware. When the optional allow_redirects.referer setting is enabled, the middleware copies the URI fragment (the portion after '#') from the referring request into the generated Referer header when following a same-scheme redirect (e.g., HTTPS to HTTPS). An attacker who controls the redirect destination can read this fragment from the incoming Referer header, potentially disclosing one-time login secrets, access tokens, state values, or other sensitive client data to a server never meant to receive it. The referer setting is disabled by default. Fixed in 7.15.1, which strips the fragment before generating the Referer value.
Source: OSV.dev (Open Source Vulnerabilities) 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 UBUNTU-CVE-2026-67354 has been found in guzzle.
Attackers can target a specific entry point like Referer header over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade guzzle to 7.15.1 or later.
If unsure, ask your IT team or search "guzzle UBUNTU-CVE-2026-67354" on the vendor's site.
UBUNTU-CVE-2026-67354 (guzzle)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: Referer header
Patched: 7.15.1 — 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 (unclassified) exists in guzzle. Attackers reach the vulnerable code path via Referer header without authentication.
Check the vendor advisory for the affected versions of guzzle. Attack surface: Referer header.
Severity: ?. Confidential information can be exposed externally.
Update to 7.15.1.
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 'guzzle' . 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 'guzzle' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
guzzleを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade guzzle to 7.15.1ステージング環境で 7.15.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- report ubuntu.com
- report cve.org
- report github.com
- report vulncheck.com