← Back
CVE-2026-59883
medium
CVSS 4.7
Information Disclosure in guzzlehttp/guzzle (CVE-2026-59883)
Summary
vulnerability in guzzlehttp/guzzle (CVE-2026-59883). Risk of unauthorized operations or information disclosure. Exploitable via ``CookieJar``. Mitigation: upgrade to `7.12.3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-59883** has been found in guzzlehttp/guzzle.
Attackers can target a specific entry point like ``CookieJar`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.7/10.
What to do: upgrade guzzlehttp/guzzle to **7.12.3** or later.
If unsure, ask your IT team or search "guzzlehttp/guzzle CVE-2026-59883" on the vendor's site.
CVE-2026-59883 (guzzlehttp/guzzle) — CWE-200 / CVSS v3 4.7
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `CookieJar` / `Domain` / `evil.192.168.0.1` / `evil.1`
Patched: `7.12.3` — apply immediately
Workaround: If you cannot upgrade immediately, do not reuse one `CookieJar` instance across untrusted and trusted origins.
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
**information disclosure** (CWE-200) exists in guzzlehttp/guzzle. Attackers reach the vulnerable code path via ``CookieJar`` without authentication.
📍 Affected scope
guzzlehttp/guzzle — . Attack surface: `CookieJar` / `Domain` / `evil.192.168.0.1` / `evil.1`.
🔥 Severity
Severity: Medium (CVSS 4.7/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **7.12.3**.
🛡️ Workaround
Workaround: If you cannot upgrade immediately, do not reuse one `CookieJar` instance across untrusted and trusted origins.
🔍 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 し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
If you cannot upgrade immediately, do not reuse one `CookieJar` instance across untrusted and trusted origins.パッチが適用されるまでの応急処置として、If you cannot upgrade immediately, do not reuse one `CookieJar` instance across untrusted and trusted origins. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade guzzlehttp/guzzle to 7.12.3ステージング環境で 7.12.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、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.12.3"}]}]
References
- web https://github.com/guzzle/guzzle/commit/b9944c161b12d9ee9c9334cfc5b9659ecd7451f8
- web https://github.com/guzzle/guzzle/pull/3694
- web https://github.com/guzzle/guzzle/releases/tag/7.12.3
- web https://github.com/guzzle/guzzle/security/advisories/GHSA-g446-98w2-8p5w
- web https://nvd.nist.gov/vuln/detail/CVE-2026-59883
- web https://github.com/advisories/GHSA-g446-98w2-8p5w