phpIPAM before 1.8.2 contains an authentication bypass vulnerability in the REST API that allows unauthenticated attackers to gain full API access… (CVE-2026-67602)
phpIPAM versions before 1.8.2 contain a critical authentication bypass vulnerability in the REST API. This flaw arises from an insecure object cache keying mechanism that allows unauthenticated attackers to gain full API access. By exploiting the cache keying issue, attackers can use a numeric database row identifier as an API token, enabling them to read, write, and delete all IP address management records.
AI Analysis
Technical Summary
The vulnerability in phpIPAM before version 1.8.2 is due to an insecure object cache keying mechanism in the REST API. The cache keys are generated based solely on lookup values without considering the searched column, which allows an entry created during an app_id lookup to be reused for an app_code lookup. This flaw permits unauthenticated attackers to bypass authentication by using the numeric database row identifier as an API token, granting full API access including reading, writing, and deleting IP address management data.
Potential Impact
Unauthenticated attackers can bypass authentication controls in the phpIPAM REST API, gaining full access to the API. This access allows them to read sensitive IP address management data, modify records, and delete information, potentially disrupting network management and exposing critical infrastructure details. The vulnerability has a CVSS score of 9.1, indicating a critical severity with high confidentiality and integrity impact but no impact on availability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict access to the phpIPAM REST API to trusted networks and users only. Monitor for unusual API activity and consider disabling the REST API if not required.
phpIPAM before 1.8.2 contains an authentication bypass vulnerability in the REST API that allows unauthenticated attackers to gain full API access… (CVE-2026-67602)
Description
phpIPAM versions before 1.8.2 contain a critical authentication bypass vulnerability in the REST API. This flaw arises from an insecure object cache keying mechanism that allows unauthenticated attackers to gain full API access. By exploiting the cache keying issue, attackers can use a numeric database row identifier as an API token, enabling them to read, write, and delete all IP address management records.
CVSS v3.1
Score 9.1critical
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in phpIPAM before version 1.8.2 is due to an insecure object cache keying mechanism in the REST API. The cache keys are generated based solely on lookup values without considering the searched column, which allows an entry created during an app_id lookup to be reused for an app_code lookup. This flaw permits unauthenticated attackers to bypass authentication by using the numeric database row identifier as an API token, granting full API access including reading, writing, and deleting IP address management data.
Potential Impact
Unauthenticated attackers can bypass authentication controls in the phpIPAM REST API, gaining full access to the API. This access allows them to read sensitive IP address management data, modify records, and delete information, potentially disrupting network management and exposing critical infrastructure details. The vulnerability has a CVSS score of 9.1, indicating a critical severity with high confidentiality and integrity impact but no impact on availability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict access to the phpIPAM REST API to trusted networks and users only. Monitor for unusual API activity and consider disabling the REST API if not required.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-368g-p5fp-42vr
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-67602"]
- Ecosystems
- []
- Database Specific Severity
- CRITICAL
- Cvss Version
- 3.1
Threat ID: 6a8c740cacd9273b49d5cf35
Added to database: 08/24/2026, 16:40:44 UTC
Last enriched: 08/24/2026, 16:52:12 UTC
Last updated: 08/25/2026, 02:26:18 UTC
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.