← Back
CVE-2026-67355
medium
CVSS 5.9
Vulnerability in guzzlehttp/guzzle (CVE-2026-67355)
Summary
vulnerability in guzzlehttp/guzzle (CVE-2026-67355). Confidential information can be exposed externally. Exploitable via ``CookieJar``. Mitigation: upgrade to `7.15.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-67355** has been found in guzzlehttp/guzzle.
Attackers can target a specific entry point like ``CookieJar`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.9/10.
What to do: upgrade guzzlehttp/guzzle to **7.15.1** or later.
If unsure, ask your IT team or search "guzzlehttp/guzzle CVE-2026-67355" on the vendor's site.
CVE-2026-67355 (guzzlehttp/guzzle) — CWE-201 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `CookieJar` / `Domain` / `example.com` / `child.example.com`
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.
❓ What is the problem
**A vulnerability** (CWE-201) exists in guzzlehttp/guzzle. Attackers reach the vulnerable code path via ``CookieJar`` without authentication.
📍 Affected scope
guzzlehttp/guzzle — . Attack surface: `CookieJar` / `Domain` / `example.com` / `child.example.com`.
🔥 Severity
Severity: Medium (CVSS 5.9/10). Confidential information can be exposed externally
🔧 How to fix
Update to **7.15.1**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'guzzlehttp/guzzle' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'guzzlehttp/guzzle' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `guzzlehttp/guzzle` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade guzzlehttp/guzzle to 7.15.1ステージング環境で 7.15.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
guzzlehttp/guzzle
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.15.1"}]}]
References
- web https://github.com/guzzle/guzzle/security/advisories/GHSA-wm3w-8rrp-j577
- web https://www.vulncheck.com/advisories/guzzlehttp-guzzle-before-host-only-cookie-scope
- web https://nvd.nist.gov/vuln/detail/CVE-2026-67355
- web https://github.com/advisories/GHSA-mjrx-74jh-7xgw
- web https://github.com/guzzle/guzzle/pull/3901
- web https://github.com/guzzle/guzzle/commit/7b68220d6543f6f80fe62e633361fc9d4ead14d4
- web https://github.com/guzzle/guzzle/releases/tag/7.15.1
- web https://github.com/advisories/GHSA-wm3w-8rrp-j577