Quick answers
- Is CVE-2026-119426 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119426 being exploited in the wild.
- How severe is CVE-2026-119426?
- High severity, with a CVSS score of 7.5, published 30 October 2026.
- Which products and versions are affected?
- phpMyAdmin through 5.2.3.
- Is there a fix for CVE-2026-119426?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-119426 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-119426?
- Check whether you run phpMyAdmin at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
phpMyAdmin constructs a PSR-7 request object from global variables before performing CSRF token validation. When a token mismatch is detected, the code clears $_POST and $_GET but the pre-built request object still contains the malicious payload. Non-AJAX POST requests to /sql and /database/sql endpoints copy the sql_query parameter from this snapshot, bypassing the token check. AJAX requests correctly abort on token mismatch. The vulnerability requires an authenticated victim session (via cookie or HTTP auth) and user interaction to visit an attacker-controlled page.
Affected products
- phpMyAdmin phpMyAdmin through 5.2.3
Timeline
- 2026-10-12: disclosed