CVE Vulnerabilities

CVE-2026-129538

Out-of-bounds Read

Published: Nov 19, 2026 | Modified: Nov 19, 2026
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
8.1 MODERATE
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Ubuntu
MEDIUM

PHP-CGI out-of-bounds read and write during PATH_INFO correction.

The PHP CGI binary (php-cgi), in CGI and FastCGI mode with cgi.fix_pathinfo enabled (the default), can perform an out-of-bounds read and write when the path removed from SCRIPT_FILENAME or PATH_TRANSLATED is longer than the supplied PATH_INFO, or when PATH_INFO is empty. This requires a web server mapping that passes such inconsistent values, or a FastCGI listener reachable by untrusted clients. An unauthenticated remote attacker can crash the process, may obtain process memory if the application exposes PATH_INFO or PATH_TRANSLATED, and may corrupt memory. PHP-FPM and the Apache module are not affected.

This issue affects PHP versions before 8.2.36, 8.3.* before 8.3.37, 8.4.* before 8.4.28 and 8.5.* before 8.5.13.

Weakness

The product reads data past the end, or before the beginning, of the intended buffer.

Affected Software

NameVendorStart VersionEnd Version
Red Hat Enterprise Linux 10RedHatphp8.4-0:8.4.28-1.el10_3*
Red Hat Enterprise Linux 10.2 Extended Update SupportRedHatphp8.4-0:8.4.28-1.el10_2*
Red Hat Enterprise Linux 8RedHatphp:7.4-8100020261119125714.f7998665*
Red Hat Enterprise Linux 9.8 Extended Update SupportRedHatphp:8.3-9080020261120133305.9*
Red Hat Enterprise Linux 9.8 Extended Update SupportRedHatphp:8.2-9080020261120141350.9*
Php5Ubuntuesm-infra-legacy/trusty*
Php7.0Ubuntuesm-infra-legacy/xenial*
Php7.2Ubuntuesm-infra/bionic*
Php7.4Ubuntuesm-infra/focal*
Php8.1Ubuntujammy*
Php8.3Ubuntunoble*
Php8.5Ubuntudevel*
Php8.5Ubunturesolute*
Php8.5Ubuntustonking*

Potential Mitigations

  • Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
  • When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
  • Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
  • To reduce the likelihood of introducing an out-of-bounds read, ensure that you validate and ensure correct calculations for any length argument, buffer size calculation, or offset. Be especially careful of relying on a sentinel (i.e. special character such as NUL) in untrusted inputs.

References