Quick answers
- Is CVE-2026-7258 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-7258 being exploited in the wild.
- How severe is CVE-2026-7258?
- High severity, with a CVSS score of 7.5, published 10 May 2026.
- Which products and versions are affected?
- PHP Group PHP 8.2.0 - 8.2.30, 8.3.0 - 8.3.30, 8.4.0 - 8.4.20, 8.5.0 - 8.5.5, 8.2.0 to 8.2.30, 8.3.0 to 8.3.30, 8.4.0 to 8.4.20, 8.5.0 to 8.5.5.
- Is there a fix for CVE-2026-7258?
- 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-7258 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-7258?
- Check whether you run PHP Group PHP 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
An out-of-bounds read vulnerability exists in PHP's urldecode() and other functions due to the improper handling of signed characters when passed to ctype functions like isxdigit(). In the affected versions, characters are cast to signed integers, which can result in negative values being passed to ctype functions. On platforms that use optimized table-lookups for these functions (notably NetBSD), this causes a negative array offset access. An attacker can trigger this by providing specially crafted URL-encoded strings, leading to a segmentation fault and subsequent denial of service. The issue is resolved in PHP versions 8.2.31, 8.3.31, 8.4.21, and 8.5.6.
Affected products
- PHP Group PHP 8.2.0 to 8.2.30, 8.3.0 to 8.3.30, 8.4.0 to 8.4.20, 8.5.0 to 8.5.5
Timeline
- 2026-05-07: advisory: GitHub advisory published by PHP maintainers
- 2026-05-10: disclosed: CVE published to NVD