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 s

Q: How do I fix CVE-2023-5676?

openj9: upgrade to 0.41.0. Exact commands for each OS are on this page.

Q: Is CVE-2023-5676 being exploited?

CVE-2023-5676 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2023-5676 affect?

CVE-2023-5676 affects openj9. Severity is medium (CVSS 4.1). 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.

Q: How urgent is CVE-2023-5676?

Priority 23/100. No elevated risk signals yet.

Routine

MEDIUM 4.1UPGRADE

CVE-2023-5676 is a medium-severity flaw (CVSS 4.1) affecting openj9. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.1 (Medium)
Attack vector	Local
Attack complexity	High
Privileges needed	High
User interaction	None
EPSS exploit chance	0.4% (top 65%)
CISA exploited list	No
Weakness	CWE-364, CWE-362
Published	2023-11-15
Last modified	2026-06-17

Publisher (CNA): Eclipse Foundation · Vendor: eclipse

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2023-11-15 14:15 UTCPublished CVE record published
2026-06-17 06:49 UTCUpdated Record last modified

eclipse openj9 UPGRADE

Affected: < 0.41.0

Fixed in: 0.41.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy openj9 || rpm -q openj9 || openj9 --version

2. UPGRADE to 0.41.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade openj9

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade openj9

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2023-5676?

openj9: upgrade to 0.41.0. Exact commands for each OS are on this page.

Is CVE-2023-5676 being exploited?

CVE-2023-5676 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2023-5676 affect?

CVE-2023-5676 affects openj9. Severity is medium (CVSS 4.1). 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 urgent is CVE-2023-5676?

Priority 23/100. No elevated risk signals yet.

Related CVEs

CVE-2026-6918 HIGH 7.5 UPGRADE In Eclipse Open9J versions 0.21 to 0.58, a pre-authentication remote attacker can crash JITServer by sending a
CVE-2026-16439 CRITICAL 9.1 UPGRADE In Eclipse OpenJ9 versions up to 0.60, using -Xtrace to trace method arguments can lead to buffer underflow.
CVE-2026-16441 CRITICAL 9.6 UPGRADE In Eclipse OpenJ9 versions up to 0.60, when executing class files where a previously concrete superclass metho
CVE-2025-4447 HIGH 7.8 UPGRADE In Eclipse OpenJ9 versions up to 0.51, when used with OpenJDK version 8 a stack based buffer overflow can be c
CVE-2024-3933 MEDIUM 5.3 UPGRADE In Eclipse OpenJ9 release versions prior to 0.44.0 and after 0.13.0, when running with JVM option -Xgc:concurr

References

← Back to latest CVEs