Heap corruption via missing XML closing tag
Published Oct 28, 2025 · Updated Oct 28, 2025
Use-after-free in Fade In 4.2.0 allows attackers to corrupt heap memory by inducing a user to open a crafted XML file. The XML parser's missing-closing-tag error path writes a null 32-bit value into a heap region it has already freed. The user must explicitly open the file because XML files are not associated with Fade In by default; the demonstrated result is a process crash, while code execution requires successful control of the corrupted heap.
Summary
What happened
Use-after-free in Fade In 4.2.0 allows attackers to corrupt heap memory by inducing a user to open a crafted XML file. The XML parser's missing-closing-tag error path writes a null 32-bit value into a heap region it has already freed. The user must explicitly open the file because XML files are not associated with Fade In by default; the demonstrated result is a process crash, while code execution requires successful control of the corrupted heap.
The record
- CVE
- CVE-2025-53814
- Published
- Oct 28, 2025
- Updated
- Oct 28, 2025
- Vendor
- GCC Productions Inc.
- Product
- Fade In
- Classifications
- CWE-416, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 28, 2025CVE publishedPublication date reported by the CVE source.
- Oct 28, 2025Record 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=4.2.0
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
- Cisco Talos malformed XML crash demonstrationproof of concept · demonstrated
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