Unauthenticated code execution via unsafe cookie deserialization
Published Aug 25, 2026 · Updated Aug 25, 2026
Insecure deserialization in TYPO3 HTML5 Video Player vs. Powermail 0 through 0.2.1 allows remote attackers to execute PHP code. An attacker-controlled cookie is passed directly to PHP's unserialize() without validation, allowing a crafted serialized object to trigger PHP Object Injection. No authentication or user interaction is required; successful exploitation executes code in the TYPO3 server context and can read, alter, or interrupt its data and service.
Summary
What happened
Insecure deserialization in TYPO3 HTML5 Video Player vs. Powermail 0 through 0.2.1 allows remote attackers to execute PHP code. An attacker-controlled cookie is passed directly to PHP's unserialize() without validation, allowing a crafted serialized object to trigger PHP Object Injection. No authentication or user interaction is required; successful exploitation executes code in the TYPO3 server context and can read, alter, or interrupt its data and service.
The record
- CVE
- CVE-2026-77138
- Published
- Aug 25, 2026
- Updated
- Aug 25, 2026
- Vendor
- in2code GmbH
- Product
- HTML5 Video Player vs. Powermail
- Classifications
- CWE-502, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 25, 2026CVE publishedPublication date reported by the CVE source.
- Aug 25, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=0.2.1
What conditions does exploitation require?
What is affected?
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