Program integrity compromise via incorrect invokeinterface dispatch
Published Jul 21, 2026 · Updated Jul 21, 2026
Incorrect method resolution in Eclipse OpenJ9 0.8.0 through 0.59.0 allows attackers to alter program behavior via crafted class files. The invokeinterface error path assumes a found abstract method belongs to an interface and performs default-method resolution instead of raising IllegalAccessError. Triggering requires a crafted class hierarchy and active user execution; the resulting wrong target can modify application state and interrupt service.
Summary
What happened
Incorrect method resolution in Eclipse OpenJ9 0.8.0 through 0.59.0 allows attackers to alter program behavior via crafted class files. The invokeinterface error path assumes a found abstract method belongs to an interface and performs default-method resolution instead of raising IllegalAccessError. Triggering requires a crafted class hierarchy and active user execution; the resulting wrong target can modify application state and interrupt service.
The record
- CVE
- CVE-2026-16441
- Published
- Jul 21, 2026
- Updated
- Jul 21, 2026
- Vendor
- The Eclipse Foundation
- Product
- Eclipse OpenJ9
- Classifications
- CWE-758, T1204.002
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 21, 2026CVE publishedPublication date reported by the CVE source.
- Jul 21, 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.8.0 <0.60.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
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