CVE-2022-3676

MEDIUMNVD 6.56.5—

6.5

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.

CVSS v3: 6.5
EG Score: 6.5(medium)
EPSS: 57.0%
KEV: Not listed

Published

October 24, 2022

Last Modified

May 7, 2025

References (6)

emo@eclipsehttps://github.com/eclipse-openj9/openj9/pull/16122
emo@eclipsehttps://github.com/eclipse/omr/pull/6773
emo@eclipsehttps://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/389
af854a3a-2127-422b-91ae-364da2661108https://github.com/eclipse-openj9/openj9/pull/16122
af854a3a-2127-422b-91ae-364da2661108https://github.com/eclipse/omr/pull/6773
af854a3a-2127-422b-91ae-364da2661108https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/389

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-29 13:43 UTCepss_batch
2026-05-29 13:43 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-26 13:43 UTCepss_batch
2026-05-26 13:43 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch

Frequently asked(5)

What is CVE-2022-3676?

CVE-2022-3676 is a medium vulnerability published on October 24, 2022. 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.

When was CVE-2022-3676 disclosed?

CVE-2022-3676 was first published in the National Vulnerability Database on October 24, 2022, with the most recent update on May 7, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2022-3676 actively exploited?

CVE-2022-3676 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 57.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2022-3676?

CVE-2022-3676 has a CVSS v3 base score of 6.5 (NVD).

How do I remediate CVE-2022-3676?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-3676, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-3676

Explore →

Is Your Infrastructure Affected by CVE-2022-3676?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2022-3676

📅 Published

🔄 Last Modified

🔗 References (6)

Weakness Classification(2)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2022-3676?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (6)

Frequently asked(5)

Related CVEs(same CWE)