CVE-2026-59883

MEDIUMPre-NVD 4.74.7—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 98% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
4.7
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.7Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Guzzle is an extensible PHP HTTP client. Prior to 7.12.3, CookieJar did not restrict cookies scoped to IP-address or bare-numeric Domain values to the exact host that set them, because SetCookie::matchesDomain() applied ordinary suffix matching to domains such as 192.168.0.1, [::1], or 1, allowing cross-host cookie disclosure, cookie injection, or session fixation. This issue is fixed in version 7.12.3.

CVSS v3
4.7
EG Score
4.7(medium)
EPSS
1.8%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 9, 2026

Advisory Details (4)

Auto-updated Jul 8, 2026
Patch available. Sources: github, github_commit, github_pr, github_release.
github Patch Available

Cookie Disclosure and Injection via IP-Address Domains in guzzlehttp/guzzle · Advisory · guzzle/guzzle · GitHub

https://github.com/guzzle/guzzle/security/advisories/GHSA-g446-98w2-8p5w
github_release Patch Available

7.12.3

Patch available: guzzle/guzzle 7.12.3

https://github.com/guzzle/guzzle/releases/tag/7.12.3
github_pr Patch Available

Treat IP cookie domains as exact-only

Patch available: guzzle/guzzle 7.12.3 (PR #3694 merged 2026-06-23)

https://github.com/guzzle/guzzle/pull/3694
github_commit Patch Available

commit b9944c161b12 (guzzle/guzzle)

Patch available: guzzle/guzzle 7.12.3 (contains commit b9944c161b12)

https://github.com/guzzle/guzzle/commit/b9944c161b12d9ee9c9334cfc5b9659ecd7451f8

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 9× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 16:40 UTCEG score recompute
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-11 08:27 UTCEPSS rescore
  4. 2026-07-10 16:36 UTCEG score recompute
  5. 2026-07-09 19:10 UTCEPSS rescore
  6. 2026-07-09 19:10 UTCEPSS rescore
  7. 2026-07-09 16:31 UTCEG score recompute
  8. 2026-07-08 16:25 UTCEG score recompute
  9. 2026-07-08 16:24 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-59883?
CVE-2026-59883 is a medium vulnerability published on July 8, 2026. Guzzle is an extensible PHP HTTP client. Prior to 7.12.3, CookieJar did not restrict cookies scoped to IP-address or bare-numeric Domain values to the exact host that set them, because SetCookie::matchesDomain() applied ordinary suffix matching to domains such as 192.168.0.1, [::1], or 1, allowing…
When was CVE-2026-59883 disclosed?
CVE-2026-59883 was first published in the National Vulnerability Database on July 8, 2026, with the most recent update on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59883 actively exploited?
CVE-2026-59883 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-59883?
CVE-2026-59883 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2026-59883?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59883, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-59883

Explore →

Is Your Infrastructure Affected by CVE-2026-59883?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs