How severe is CVE-2023-5676?

CVE-2023-5676 has a CVSS 3.x base score of 4.1, rated medium severity. It is exploitable over local access with high attack complexity, requires high privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2023-5676 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (33rd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2023-5676?

CVE-2023-5676 affects Eclipse Openj9. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2023-5676?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2023-5676 published?

CVE-2023-5676 was published on 2023-11-15 and last updated on 2026-06-17.

CVE-2023-5676

CVE-2023-5676 is a medium-severity vulnerability in Eclipse Openj9 with a CVSS 3.x base score of 4.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-362.

Key facts

Severity: Medium (CVSS 3.x base score 4.1)
EPSS exploit prediction: 0% (33rd percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-362
Affected product: Eclipse Openj9
Published: 2023-11-15
Last modified: 2026-06-17

Description

In Eclipse OpenJ9 before version 0.41.0, the JVM can be forced into an infinite busy hang on a spinlock or a segmentation fault if a shutdown signal (SIGTERM, SIGINT or SIGHUP) is received before the JVM has finished initializing.

Frequently asked questions

What is CVE-2023-5676?: In Eclipse OpenJ9 before version 0.41.0, the JVM can be forced into an infinite busy hang on a spinlock or a segmentation fault if a shutdown signal (SIGTERM, SIGINT or SIGHUP) is received before the JVM has finished initializing.
How severe is CVE-2023-5676?: CVE-2023-5676 has a CVSS 3.x base score of 4.1, rated medium severity. It is exploitable over local access with high attack complexity, requires high privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2023-5676 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (33rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2023-5676?: CVE-2023-5676 affects Eclipse Openj9. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2023-5676?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2023-5676 published?: CVE-2023-5676 was published on 2023-11-15 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:eclipse:openj9:*:*:*:*:*:*:*:*

More vulnerabilities in Eclipse Openj9

CVE-2021-41035 — Critical (CVSS 9.8): In Eclipse Openj9 before version 0.29.0, the JVM does not throw IllegalAccessError for MethodHandles that invoke…
CVE-2020-27221 — Critical (CVSS 9.8): In Eclipse OpenJ9 up to and including version 0.23, there is potential for a stack-based buffer overflow when the…
CVE-2019-11772 — Critical (CVSS 9.8): In Eclipse OpenJ9 prior to 0.15, the String.getBytes(int, int, byte[], int) method does not verify that the provided…
CVE-2018-12549 — Critical (CVSS 9.8): In Eclipse OpenJ9 version 0.11.0, the OpenJ9 JIT compiler may incorrectly omit a null check on the receiver object of…
CVE-2018-12547 — Critical (CVSS 9.8): In Eclipse OpenJ9, prior to the 0.12.0 release, the jio_snprintf() and jio_vsnprintf() native methods ignored the…
CVE-2018-12548 — Critical (CVSS 9.8): In OpenJDK + Eclipse OpenJ9 version 0.11.0 builds, the public jdk.crypto.jniprovider.NativeCrypto class contains public…

All CVEs affecting Eclipse Openj9 →

Other CWE-362 (Race Condition) vulnerabilities

CVE-2022-27626 — Critical (CVSS 10.0): A vulnerability regarding concurrent execution using shared resource with improper synchronization ('Race Condition')…
CVE-2015-8556 — Critical (CVSS 10.0): Local privilege escalation vulnerability in the Gentoo QEMU package before 2.5.0-r1.
CVE-2014-0703 — Critical (CVSS 10.0): Cisco Wireless LAN Controller (WLC) devices 7.4 before 7.4.110.0 distribute Aironet IOS software with a race condition…
CVE-2010-1228 — Critical (CVSS 10.0): Multiple race conditions in the sandbox infrastructure in Google Chrome before 4.1.249.1036 have unspecified impact and…
CVE-2008-6598 — Critical (CVSS 10.0): Multiple race conditions in WANPIPE before 3.3.6 have unknown impact and attack vectors related to "bri restart logic."
CVE-2026-46137 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: ADD_ADDR rtx: fix potential…

Browse all CWE-362 (Race Condition) vulnerabilities →