Arbitrary code execution via unsafe XML deserialization
Published Nov 21, 2024 · Updated Jul 5, 2026
Arbitrary code execution in OmegaT 6.0.1 allows attackers to run code when a crafted segmentation.conf file is loaded. The SRX class passes the user-writable segmentation.conf file to Java XMLDecoder, which instantiates attacker-specified objects and invokes their methods during startup. Exploitation requires placing the file in the user's OmegaT configuration directory; the public proof of concept launches a process with that user's privileges when OmegaT starts.
Summary
What happened
Arbitrary code execution in OmegaT 6.0.1 allows attackers to run code when a crafted segmentation.conf file is loaded. The SRX class passes the user-writable segmentation.conf file to Java XMLDecoder, which instantiates attacker-specified objects and invokes their methods during startup. Exploitation requires placing the file in the user's OmegaT configuration directory; the public proof of concept launches a process with that user's privileges when OmegaT starts.
The record
- CVE
- CVE-2024-51366
- Published
- Nov 21, 2024
- Updated
- Jul 5, 2026
- Vendor
- OmegaT
- Product
- OmegaT
- Classifications
- CWE-434, T1203
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 21, 2024CVE publishedPublication date reported by the CVE source.
- Jul 5, 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=6.0.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
- OmegaT 6.0.1 segmentation.conf proof of conceptproof 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