In Eclipse Openj9 before version 0.35.0, interface calls can be inlined without a runtime type check. Malicious bytecode could make use of…

Description

In Eclipse Openj9 before version 0.35.0, interface calls can be inlined without a runtime type check. Malicious bytecode could make use of this inlining to access or modify memory via an incompatible type.

Scores

EPSS (exploitation in 30 days)

0.81% · top 43% of all CVEs (6 Nov 2026)

CISA SSVC

Exploitation: none · Automatable: no · Technical impact: partial

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.5.

Weakness

• CWE-20: Improper Input Validation (opens in a new tab)All about CWE-20 and its CVEs
• CWE-843: Access of Resource Using Incompatible Type ('Type Confusion') (opens in a new tab)All about CWE-843 and its CVEs

Affected products

• The Eclipse Foundation · Eclipse OpenJ9

  • affected unspecified – < 0.35.0

References (3)

• https://github.com/eclipse-openj9/openj9/pull/16122 (opens in a new tab)x_transferred
• https://github.com/eclipse/omr/pull/6773 (opens in a new tab)x_transferred
• https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/389 (opens in a new tab)x_transferred

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisories (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2022-3676](https://trackcve.app/badge/CVE-2022-3676.svg)](https://trackcve.app/cve/CVE-2022-3676)

Record last updated 7 May 2025, 15:59 UTC.