CVE-2026-67602

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreHIGH confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-24. a secondary CVSS source baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: None knownExposed: 0

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

phpIPAM before 1.8.2 contains an authentication bypass vulnerability in the REST API that allows unauthenticated attackers to gain full API access by exploiting an insecure object cache keying mechanism. The cache is keyed by lookup value alone without including the searched column, enabling an entry written during an app_id lookup to satisfy a subsequent app_code lookup, allowing attackers to use the numeric database row identifier as an API token to read, write, and delete all IP address management records.

CVSS v3
9.1
EG Score
9.1(high)
EG Risk
56(Track)
EG Risk 56/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

August 24, 2026

Last Modified

August 24, 2026

Advisory Details (3)

Auto-updated Aug 24, 2026
Patch available. Sources: github_release, github_commit.
generic

phpIPAM < 1.8.2 Authentication Bypass via REST API Object Cache | Advisories | VulnCheck

https://www.vulncheck.com/advisories/phpipam-authentication-bypass-via-rest-api-object-cache
github_commit Patch Available

commit d29728fecca3 (phpipam/phpipam)

Patch available: phpipam/phpipam v1.8.2 (contains commit d29728fecca3)

https://github.com/phpipam/phpipam/commit/d29728fecca327f1ea825798908d0cfa4c62408e
github_release Patch Available

1.8.2

Patch available: phpipam/phpipam v1.8.2

https://github.com/phpipam/phpipam/releases/tag/v1.8.2

Vendor Advisories for CVE-2026-67602(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 19× 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-08-26 06:24 UTCGHSA enrichment
  2. 2026-08-26 01:58 UTCGHSA enrichment
  3. 2026-08-25 21:40 UTCGHSA enrichment
  4. 2026-08-25 17:03 UTCEG score recompute
  5. 2026-08-25 17:03 UTCGHSA enrichment
  6. 2026-08-25 13:49 UTCEPSS rescore
  7. 2026-08-25 12:43 UTCGHSA enrichment
  8. 2026-08-25 08:24 UTCGHSA enrichment
  9. 2026-08-25 04:02 UTCGHSA enrichment
  10. 2026-08-24 23:43 UTCGHSA enrichment
  11. 2026-08-24 19:25 UTCEG score recompute
  12. 2026-08-24 19:25 UTCGHSA enrichment
  13. 2026-08-24 19:07 UTCEG score recompute
  14. 2026-08-24 19:07 UTCGHSA enrichment
  15. 2026-08-24 18:43 UTCEG score recompute
  16. 2026-08-24 18:43 UTCGHSA enrichment
  17. 2026-08-24 14:24 UTCEG score recompute
  18. 2026-08-24 14:02 UTCEG score recompute
  19. 2026-08-24 14:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-67602?
CVE-2026-67602 is a critical vulnerability published on August 24, 2026. phpIPAM before 1.8.2 contains an authentication bypass vulnerability in the REST API that allows unauthenticated attackers to gain full API access by exploiting an insecure object cache keying mechanism. The cache is keyed by lookup value alone without including the searched column, enabling an…
When was CVE-2026-67602 disclosed?
CVE-2026-67602 was first published in the National Vulnerability Database on August 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-67602 actively exploited?
CVE-2026-67602 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 72.1% of all scored CVEs.
What is the CVSS score of CVE-2026-67602?
CVE-2026-67602 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-67602?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-67602, 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-67602

Explore →

Is Your Infrastructure Affected by CVE-2026-67602?

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

Start Free Scan →Browse All CVEs