# CVE-2026-67602: phpIPAM < 1.8.2 Authentication Bypass via REST API Object Cache

> Unauthenticated attackers can bypass REST API authentication in phpIPAM to read, write, and delete all IP address management records.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Aug 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-368g-p5fp-42vr

## What is CVE-2026-67602?

CVE-2026-67602 is a critical authentication bypass vulnerability in phpipam, published on 24 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-706 (Use of Incorrectly-Resolved Name or Reference)

## Which versions are affected by CVE-2026-67602?


## How do I fix CVE-2026-67602?

No fix has been published for CVE-2026-67602 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-67602 being exploited?

There is no known exploitation of CVE-2026-67602 in the wild and no public exploit code.

Public exploit code:

- https://github.com/Hunt-Benito/the-token-was-a-row-number-cve-2026-67602-phpipam-rest-api-authentication-bypass (github_poc): https://github.com/Hunt-Benito/the-token-was-a-row-number-cve-2026-67602-phpipam-rest-api-authentication-bypass

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-67602 and fix it if it is affected.

What it is: CVE-2026-67602 is a critical authentication bypass vulnerability in phpipam, published on 24 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-67602 in the wild and no public exploit code.

Affected product: phpipam. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-67602/ (Markdown: https://insights.sbomify.com/CVE-2026-67602/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-67602
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-67602
- OSV: https://osv.dev/vulnerability/CVE-2026-67602

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-67602/
Summaries are generated and may contain mistakes; the official description above is the record.