phpIPAM through 1.8.3 has incorrect authorization for id=="admins" and id=="all" in api/controllers/User.php.
CVE-2026-97818
This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.6
- EG Score
- 8.6(low)
- EG Risk
- 43(Track)EG Risk 43/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 computedSeverity86% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 25, 2026
Last Modified
September 25, 2026
Advisory Details (2)
Auto-updated Sep 25, 2026phpipam/api/controllers/User.php at e8010751d491e485acefa5787fb0e518eb948771 · phpipam/phpipam · GitHub
https://github.com/phpipam/phpipam/blob/e8010751d491e485acefa5787fb0e518eb948771/api/controllers/User.php#L143-L1461.8.3
Patch available: phpipam/phpipam v1.8.3
https://github.com/phpipam/phpipam/releases/tag/v1.8.3Vendor Advisories for CVE-2026-97818(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 3× in last 7d / 3× 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.
- 2026-09-25 05:26 UTCEG score recompute
- 2026-09-25 04:57 UTCEG score recompute
- 2026-09-25 04:57 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-97818?
When was CVE-2026-97818 disclosed?
What is the CVSS score of CVE-2026-97818?
How do I remediate CVE-2026-97818?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-97818
Is Your Infrastructure Affected by CVE-2026-97818?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.