sebastianbergmann phpunit up to 12.5.7 cleanupForCoverage deserialization

Summaryinfo

A vulnerability was found in sebastianbergmann phpunit up to 8.5.51/9.6.32/10.5.61/11.5.49/12.5.7 and classified as problematic. The impacted element is the function cleanupForCoverage. Such manipulation leads to deserialization. This vulnerability is referenced as CVE-2026-24765. The attack can only be performed from a local environment. No exploit is available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in sebastianbergmann phpunit up to 8.5.51/9.6.32/10.5.61/11.5.49/12.5.7 and classified as problematic. Affected by this issue is the function cleanupForCoverage. The manipulation with an unknown input leads to a deserialization vulnerability. Using CWE to declare the problem leads to CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. Impacted is confidentiality, integrity, and availability. CVE summarizes:

PHPUnit is a testing framework for PHP. A vulnerability has been discovered in versions prior to 12.5.8, 11.5.50, 10.5.62, 9.6.33, and 8.5.52 involving unsafe deserialization of code coverage data in PHPT test execution. The vulnerability exists in the `cleanupForCoverage()` method, which deserializes code coverage files without validation, potentially allowing remote code execution if malicious `.coverage` files are present prior to the execution of the PHPT test. The vulnerability occurs when a `.coverage` file, which should not exist before test execution, is deserialized without the `allowed_classes` parameter restriction. An attacker with local file write access can place a malicious serialized object with a `__wakeup()` method into the file system, leading to arbitrary code execution during test runs with code coverage instrumentation enabled. This vulnerability requires local file write access to the location where PHPUnit stores or expects code coverage files for PHPT tests. This can occur through CI/CD pipeline attacks, the local development environment, and/or compromised dependencies. Rather than just silently sanitizing the input via `['allowed_classes' => false]`, the maintainer has chosen to make the anomalous state explicit by treating pre-existing `.coverage` files for PHPT tests as an error condition. Starting in versions in versions 12.5.8, 11.5.50, 10.5.62, 9.6.33, when a `.coverage` file is detected for a PHPT test prior to execution, PHPUnit will emit a clear error message identifying the anomalous state. Organizations can reduce the effective risk of this vulnerability through proper CI/CD configuration, including ephemeral runners, code review enforcement, branch protection, artifact isolation, and access control.

The advisory is available at github.com. This vulnerability is handled as CVE-2026-24765 since 01/26/2026. The exploitation is known to be easy. Local access is required to approach this attack. Technical details are known, but there is no available exploit.

The vulnerability scanner Nessus provides a plugin with the ID 297036 (Linux Distros Unpatched Vulnerability : CVE-2026-24765), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 8.5.52, 9.6.33, 10.5.62, 11.5.50 or 12.5.8 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 3141742e00620e2968d3d2e732d320de76685fda is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (297036) and EUVD (EUVD-2026-4725). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

• sebastianbergmann

Name

• phpunit

Version

• 8.5.0
• 8.5.1
• 8.5.2
• 8.5.3
• 8.5.4
• 8.5.5
• 8.5.6
• 8.5.7
• 8.5.8
• 8.5.9
• 8.5.10
• 8.5.11
• 8.5.12
• 8.5.13
• 8.5.14
• 8.5.15
• 8.5.16
• 8.5.17
• 8.5.18
• 8.5.19
• 8.5.20
• 8.5.21
• 8.5.22
• 8.5.23
• 8.5.24
• 8.5.25
• 8.5.26
• 8.5.27
• 8.5.28
• 8.5.29
• 8.5.30
• 8.5.31
• 8.5.32
• 8.5.33
• 8.5.34
• 8.5.35
• 8.5.36
• 8.5.37
• 8.5.38
• 8.5.39
• 8.5.40
• 8.5.41
• 8.5.42
• 8.5.43
• 8.5.44
• 8.5.45
• 8.5.46
• 8.5.47
• 8.5.48
• 8.5.49
• 8.5.50
• 8.5.51
• 9.6.0
• 9.6.1
• 9.6.2
• 9.6.3
• 9.6.4
• 9.6.5
• 9.6.6
• 9.6.7
• 9.6.8
• 9.6.9
• 9.6.10
• 9.6.11
• 9.6.12
• 9.6.13
• 9.6.14
• 9.6.15
• 9.6.16
• 9.6.17
• 9.6.18
• 9.6.19
• 9.6.20
• 9.6.21
• 9.6.22
• 9.6.23
• 9.6.24
• 9.6.25
• 9.6.26
• 9.6.27
• 9.6.28
• 9.6.29
• 9.6.30
• 9.6.31
• 9.6.32
• 10.5.0
• 10.5.1
• 10.5.2
• 10.5.3
• 10.5.4
• 10.5.5
• 10.5.6
• 10.5.7
• 10.5.8
• 10.5.9
• 10.5.10
• 10.5.11
• 10.5.12
• 10.5.13
• 10.5.14
• 10.5.15
• 10.5.16
• 10.5.17
• 10.5.18
• 10.5.19
• 10.5.20
• 10.5.21
• 10.5.22
• 10.5.23
• 10.5.24
• 10.5.25
• 10.5.26
• 10.5.27
• 10.5.28
• 10.5.29
• 10.5.30
• 10.5.31
• 10.5.32
• 10.5.33
• 10.5.34
• 10.5.35
• 10.5.36
• 10.5.37
• 10.5.38
• 10.5.39
• 10.5.40
• 10.5.41
• 10.5.42
• 10.5.43
• 10.5.44
• 10.5.45
• 10.5.46
• 10.5.47
• 10.5.48
• 10.5.49
• 10.5.50
• 10.5.51
• 10.5.52
• 10.5.53
• 10.5.54
• 10.5.55
• 10.5.56
• 10.5.57
• 10.5.58
• 10.5.59
• 10.5.60
• 10.5.61
• 11.5.0
• 11.5.1
• 11.5.2
• 11.5.3
• 11.5.4
• 11.5.5
• 11.5.6
• 11.5.7
• 11.5.8
• 11.5.9
• 11.5.10
• 11.5.11
• 11.5.12
• 11.5.13
• 11.5.14
• 11.5.15
• 11.5.16
• 11.5.17
• 11.5.18
• 11.5.19
• 11.5.20
• 11.5.21
• 11.5.22
• 11.5.23
• 11.5.24
• 11.5.25
• 11.5.26
• 11.5.27
• 11.5.28
• 11.5.29
• 11.5.30
• 11.5.31
• 11.5.32
• 11.5.33
• 11.5.34
• 11.5.35
• 11.5.36
• 11.5.37
• 11.5.38
• 11.5.39
• 11.5.40
• 11.5.41
• 11.5.42
• 11.5.43
• 11.5.44
• 11.5.45
• 11.5.46
• 11.5.47
• 11.5.48
• 11.5.49
• 12.5.0
• 12.5.1
• 12.5.2
• 12.5.3
• 12.5.4
• 12.5.5
• 12.5.6
• 12.5.7

License

• open-source

Website

• Product: https://github.com/sebastianbergmann/phpunit/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion