Approved changes feed: RSS · Atom
cpe:2.3:a:eclipse_foundation:openj9:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Eclipse Foundation (2c315c48-0111-5572-bbde-cc70cfafb2e9) |
|---|---|
| Product | Openj9 (86555e95-6644-526a-a8eb-4e04c4b561af) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-16441 |
vulnerable | 2026-07-29 00:26:18.689446 |
Eclipse OpenJ9 : Method resolution default method precedence failure
In Eclipse OpenJ9 versions up to 0.60, when executing class files where a previously concrete superclass method has been recompiled as abstract, execution is incorrectly delegated to an interface default method.
Published: 2026-07-21T18:07:02.798Z
Updated: 2026-07-22T19:07:14.315Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-16439 |
vulnerable | 2026-07-29 00:26:18.689129 |
Eclipse OpenJ9 : Using -Xtrace to trace method arguments can lead to buffer underflow
In Eclipse OpenJ9 versions up to 0.60, using -Xtrace to trace method arguments can lead to buffer underflow.
Published: 2026-07-21T17:28:44.409Z
Updated: 2026-07-22T18:27:00.671Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-4447 |
vulnerable | 2026-06-08 07:29:16.259642 |
Buffer Overflow in Eclipse OpenJ9
In Eclipse OpenJ9 versions up to 0.51, when used with OpenJDK version 8 a stack based buffer overflow can be caused by modifying a file on disk that is read when the JVM starts.
Published: 2025-05-09T20:40:25.953Z
Updated: 2025-05-10T01:46:54.369Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-5676 |
vulnerable | 2026-06-08 06:19:44.426542 |
Eclipse OpenJ9 possible infinite busy hang
MEDIUM (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.
Published: 2023-11-15T14:02:01.422Z
Updated: 2025-11-03T21:50:38.622Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.