Security readout for executives and security teams
Plain-English summary
PHPUnit can execute malicious code during certain test runs if an attacker can plant a crafted coverage file beforehand. This is mainly a CI/CD, developer workstation, or dependency-compromise risk, not a typical internet-facing service bug. The business priority is protecting build pipelines and upgrading PHPUnit in affected projects.
Executive priority
Treat as high priority for engineering and DevSecOps teams using PHPUnit. Focus on CI/CD hardening and dependency trust because successful exploitation can compromise build runners, secrets, and release integrity. Internet perimeter teams are less likely to be directly affected unless test tooling is exposed improperly.
Technical view
CVE-2026-24765 is unsafe deserialization in PHPUnit PHPT code coverage handling. The cleanupForCoverage() path deserializes pre-existing .coverage files without class restrictions. With local file write access to the expected coverage location, a malicious serialized object can run code during PHPT tests with coverage instrumentation enabled. CWE-502; CVSS 7.8.
Likely exposure
Exposure is most likely where affected PHPUnit versions run PHPT tests with code coverage in CI, local development, or package build environments. Attackers need local file write access to the relevant coverage-file location, such as through compromised dependencies, weak pipeline isolation, or malicious repository changes.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation requires a pre-positioned malicious .coverage file before PHPT execution. This makes the issue more constrained than remote unauthenticated RCE, but serious in trusted build environments.
Researcher notes
The vulnerable condition is anomalous pre-existing .coverage files for PHPT tests. The fix makes that state an explicit error rather than silently deserializing. The source bundle has a minor version-reference inconsistency around the 10.5.x release, so confirm exact fixed package versions against vendor and distro advisories.
Mitigation direction
- Upgrade PHPUnit to the vendor-advised fixed release for your supported branch.
- Use 8.5.52, 9.6.33, 10.5.62 or later, 11.5.50, or 12.5.8.
- Review vendor advisories for exact branch guidance and packaging updates.
- Use ephemeral CI runners and isolate build artifacts between jobs.
- Restrict write access to test workspaces and coverage-file locations.
- Enforce code review, branch protection, and dependency integrity controls.
Validation and detection
- Inventory repositories and build images for PHPUnit versions in affected ranges.
- Identify CI jobs running PHPT tests with code coverage enabled.
- Check whether build workspaces persist files across jobs or pull requests.
- Confirm upgraded PHPUnit behavior errors on pre-existing PHPT .coverage files.
- Review Debian LTS guidance if using Debian-packaged PHPUnit.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-24765 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/sebastianbergmann/phpunit/security/advisories/GHSA-vvj3-c3rp-c85pCVE reference · x_refsource_CONFIRM
- https://github.com/sebastianbergmann/phpunit/commit/3141742e00620e2968d3d2e732d320de76685fdaCVE reference · x_refsource_MISC
- https://github.com/sebastianbergmann/phpunit/releases/tag/10.5.63CVE reference · x_refsource_MISC
- https://github.com/sebastianbergmann/phpunit/releases/tag/11.5.50CVE reference · x_refsource_MISC
- https://github.com/sebastianbergmann/phpunit/releases/tag/12.5.8CVE reference · x_refsource_MISC
- https://github.com/sebastianbergmann/phpunit/releases/tag/8.5.52CVE reference · x_refsource_MISC
- https://github.com/sebastianbergmann/phpunit/releases/tag/9.6.33CVE reference · x_refsource_MISC
- https://lists.debian.org/debian-lts-announce/2026/02/msg00009.htmlCVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
