CVE-2026-67602
Auth bypass in phpIPAM REST API enables full API access via cache key flaw.
Is CVE-2026-67602 being exploited?
Not confirmed. CVE-2026-67602 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.35% probability of exploitation in the next 30 days.
How severe is CVE-2026-67602?
CVE-2026-67602 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-67602?
Yes. A fix has been recorded for CVE-2026-67602. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-67602 affect?
CVE-2026-67602 affects phpIPAM < 1.8.2, phpIPAM REST API, IPAM deployments using phpIPAM. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67602?
Upgrade to phpIPAM 1.8.2+, restrict API access, rotate API tokens/credentials.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attackers can read, create, modify, and delete all IPAM records by using a numeric DB row ID as an API token.
Immediate action required
- affected< 1.8.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.