CVSS 4.0
2.1 lowCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:PCVE-2026-121261
Low (2.1). EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
A vulnerability has been found in phpMyAdmin ShapeFile up to 4.0.1. Impacted is the function ShapeRecord::loadFromFile of the component SHP File Handler. Such manipulation leads to infinite loop. The attack can be executed remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
Severity
CVSS 3.1
4.3 mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L- EPSS
- 0.3% estimated probability of exploitation activity in the next 30 days; 22nd percentile. Scored 2026-11-04. A forecast for this CVE across the internet, not for your own systems.
- CWEs
- CWE-404 Improper Resource Shutdown or Release
CWE-835 Loop with Unreachable Exit Condition (Infinite Loop) - Published
- Modified
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-121261 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-121261?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-121261?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-121261 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| phpMyAdmin ShapeFile | 4.0.0 |
| phpMyAdmin ShapeFile | 4.0.1 |
Attack patterns (CAPEC)
- CAPEC-125 Flooding Likelihood: High · Severity: Medium
- CAPEC-130 Excessive Allocation Likelihood: Medium · Severity: Medium
- CAPEC-131 Resource Leak Exposure Likelihood: Medium · Severity: Medium
- CAPEC-494 TCP Fragmentation
- CAPEC-495 UDP Fragmentation
- CAPEC-496 ICMP Fragmentation
- CAPEC-666 BlueSmacking Likelihood: Medium · Severity: Medium
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.