# CVE-2026-121262: phpMyAdmin SQL-Parser ExplainStatement.php parse type conversion


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-121262, GHSA-p9h2-47v4-hgjj, UBUNTU-CVE-2026-121262

## What is CVE-2026-121262?

CVE-2026-121262 is a medium-severity vulnerability in phpMyAdmin SQL-Parser, published on 3 Nov 2026. 

### Official description

A vulnerability was found in phpMyAdmin SQL-Parser 6.0.0/6.0.1. The affected element is the function parse of the file src/Statements/ExplainStatement.php. Performing a manipulation of the argument nextToken results in incorrect type conversion. The attack is possible to be carried out remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-704 (Incorrect Type Conversion or Cast)

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

It affects 1 product.


Products: Phpmyadmin Sql-Parser.

CPE match criteria (CPE 2.3):

- `cpe:2.3:a:phpmyadmin:sql-parser:*:*:*:*:*:*:*:*` from 6.0.0 up to 6.0.0
- `cpe:2.3:a:phpmyadmin:sql-parser:*:*:*:*:*:*:*:*` from 6.0.1 up to 6.0.1

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

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

## Is CVE-2026-121262 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-121262 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-121262 is a medium-severity vulnerability in phpMyAdmin SQL-Parser, published on 3 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-121262 exists.

Affected product: phpMyAdmin SQL-Parser. 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-121262/ (Markdown: https://insights.sbomify.com/CVE-2026-121262/index.md)
```

## Sources

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

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