Code execution via unverified Redis session deserialization
Published May 1, 2026 · Updated May 1, 2026
Unsafe deserialization in MixPHP Framework 2.x through 2.2.17 allows attackers to execute code through crafted Redis session data. The Redis-backed session handler passes stored values directly to PHP unserialize() without an integrity check or an allowed-class restriction. Exploitation requires control of the backing Redis store, or another weakness that permits injection into it, and executes a PHP POP chain on the application server.
Summary
What happened
Unsafe deserialization in MixPHP Framework 2.x through 2.2.17 allows attackers to execute code through crafted Redis session data. The Redis-backed session handler passes stored values directly to PHP unserialize() without an integrity check or an allowed-class restriction. Exploitation requires control of the backing Redis store, or another weakness that permits injection into it, and executes a PHP POP chain on the application server.
The record
- CVE
- CVE-2026-42472
- Published
- May 1, 2026
- Updated
- May 1, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-502
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- May 1, 2026CVE publishedPublication date reported by the CVE source.
- May 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo