How broadly exploitable is this vulnerability?

It is exploitable wherever FrankenPHP is used in worker mode with sessions, and an attacker can send normal HTTP requests to the application. The attacker does not need special privileges, but exploitation depends on being scheduled onto a worker that has just processed another user's request and on the application's use of `$_SESSION` before proper initialization.

Does an attacker need to be authenticated to exploit it?

Not necessarily. An unauthenticated attacker can potentially receive residual session data from a prior authenticated user if they happen to be served by the same worker and the application reads from `$_SESSION` early. However, the exact impact depends on how the application uses sessions and what data is stored there.

What is the safest general fix pattern for this class of issue?

The safest approach is to enforce

Severity:

HIGH RISK

(7.5)

Session Data Isolation Failure (CWE-384) in FrankenPHP Worker Mode

CVE-2026-24894

Published:

Feb 12, 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-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setGameSpeedCfg CGI Handler

Remote Code Execution on the Router

April 6, 2026

CWE-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setFirewallType Handler

Remote Code Execution on Router Firmware

April 6, 2026

Vulnerability Type

Category:

Session Management Vulnerability

CWE:

CWE-269;CWE-384;CWE-613

Impact:

Unauthorized Access to Session Data / Session Confidentiality Breach

Severity:

HIGH RISK

(7.5)

CVSS Version:

3.1

Vulnerability Type

Category:

Session Management Vulnerability

CWE:

CWE-269;CWE-384;CWE-613

Impact:

Unauthorized Access to Session Data / Session Confidentiality Breach

Severity:

HIGH RISK

(7.5)

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

Session Data Isolation Failure (CWE-384) in FrankenPHP Worker Mode

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

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setGameSpeedCfg CGI Handler

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setFirewallType Handler

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