Code execution via oversized configuration path
Published Feb 18, 2026 · Updated Feb 18, 2026
Stack-based buffer overflow in ChaosPro 2.0 allows attackers to execute arbitrary code through a crafted ChaosPro.cfg file. The parser copies an oversized PicturePath or ProfilePath value from ChaosPro.cfg into a fixed-size stack buffer, overwriting the SEH record. Execution requires a user to run ChaosPro with the malicious local configuration on Windows XP; the demonstrated payload starts a bind shell.
Summary
What happened
Stack-based buffer overflow in ChaosPro 2.0 allows attackers to execute arbitrary code through a crafted ChaosPro.cfg file. The parser copies an oversized PicturePath or ProfilePath value from ChaosPro.cfg into a fixed-size stack buffer, overwriting the SEH record. Execution requires a user to run ChaosPro with the malicious local configuration on Windows XP; the demonstrated payload starts a bind shell.
The record
- CVE
- CVE-2019-25365
- Published
- Feb 18, 2026
- Updated
- Feb 18, 2026
- Vendor
- Martin Pfingstl
- Product
- ChaosPro
- Classifications
- CWE-121, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 18, 2026CVE publishedPublication date reported by the CVE source.
- Feb 18, 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=2.0
What conditions does exploitation require?
What is affected?
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
- ChaosPro 2.0 - Buffer Overflow (SEH)functional · 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