Is this vulnerability remotely exploitable over the network?

Not directly. Exploitation requires the ability to write malicious `.coverage` files to the filesystem location PHPUnit uses for PHPT coverage data. However, this access can often be achieved indirectly through compromised CI jobs, poisoned dependencies, or insider access to build infrastructure, which may originate from remote attacks.

What level of access does an attacker need to exploit this issue?

The attacker needs local file write access to the directory where PHPUnit expects or stores `.coverage` files for PHPT tests. This might be obtained via a compromised CI runner, misconfigured permissions on shared build directories, malicious code in a dependency, or a local user account with access to the development or build machine.

What is the safest general fix pattern for similar issues?

The safest pattern is to never deserialize data from disk or external sources without treating it as untrusted. Use strong invariants: ensure artifacts are created fresh for each run, treat pre-existing files as errors, and, where deserialization is necessary, explicitly restrict allowed classes and validate the data structure before use. In many cases, replacing serialization-based formats with safer, structured formats (e.g., JSON with schema validation) is preferable.

Severity:

HIGH RISK

(7.8)

Unsafe Deserialization of Coverage Data (CWE-502) in PHPUnit PHPT Test Execution

CVE-2026-24765

Published:

Jan 27, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-78

CRITICAL RISK

CRITICAL

(9.9)

Command Injection in MCP Stdio Configuration Validation (CWE-78) in WeKnora

Remote Code Execution

March 7, 2026

CWE-89

CRITICAL RISK

CRITICAL

(9.9)

SQL Injection via PostgreSQL Array/Row Expressions (CWE-89) in WeKnora Query Engine

Remote Code Execution via SQL Injection on the Database Server

March 7, 2026

Vulnerability Type

Category:

Unsafe Deserialization

CWE:

CWE-502

Impact:

Remote Code Execution in Local/CI Environments

Severity:

HIGH RISK

(7.8)

CVSS Version:

3.1

Vulnerability Type

Category:

Unsafe Deserialization

CWE:

CWE-502

Impact:

Remote Code Execution in Local/CI Environments

Severity:

HIGH RISK

(7.8)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

START 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Unsafe Deserialization of Coverage Data (CWE-502) in PHPUnit PHPT Test Execution

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

CRITICAL RISK

CRITICAL

(9.9)

Command Injection in MCP Stdio Configuration Validation (CWE-78) in WeKnora

CRITICAL RISK

CRITICAL

(9.9)

SQL Injection via PostgreSQL Array/Row Expressions (CWE-89) in WeKnora Query Engine

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare