CVE-2026-91487: 
Amazon Corretto JDK Schwachstellenanalyse und -minderung

Überblick

CVE-2026-91487 is a vulnerability in the Compiler component (C2 comparisons) of Oracle Java SE that allows an unauthenticated network attacker to perform unauthorized read and write operations on data accessible to the affected Java SE instance. It was disclosed on October 20, 2026, as part of Oracle's October 2026 Critical Patch Update (CPU). Affected versions include Oracle Java SE 8u503-perf, 11.0.32.1, 17.0.20.1, 21.0.12.1, 25.0.4.1, and 27; Oracle GraalVM for JDK 17.0.20.1 and 21.0.12.1; and Oracle GraalVM Enterprise Edition 21.3.19.1.1. The vulnerability carries a CVSS v3.1 base score of 4.8 (Medium) (Oracle CPU Oct 2026, Red Hat Bugzilla).

Technische Details

The vulnerability is rooted in improper comparison logic within the Java C2 JIT compiler, classified under CWE-1025 (Comparison Using Wrong Factors) and CWE-284 (Improper Access Control). An unauthenticated attacker with network access can exploit this flaw by supplying crafted data to the Compiler APIs via multiple network protocols (e.g., HTTP, HTTPS, or other supported protocols). Exploitation is constrained to scenarios where data is supplied directly to the Compiler APIs — it cannot be triggered via Untrusted Java Web Start applications or Untrusted Java applets. The high attack complexity (AC:H) reflects the difficulty in reliably triggering the faulty comparison behavior (Oracle CPU Oct 2026, Red Hat Bugzilla).

Auswirkungen

Successful exploitation results in limited confidentiality and integrity impacts: an attacker can gain unauthorized read access to a subset of Oracle Java SE accessible data and perform unauthorized update, insert, or delete operations on some accessible data. Availability is not impacted. The scope is unchanged, meaning the vulnerability does not enable privilege escalation beyond the Java SE process boundary, and lateral movement potential is limited given the constrained attack surface (Oracle CPU Oct 2026).

Ausnutzbarkeit

There is no public proof-of-concept exploit and no evidence of in-the-wild exploitation as of the time of disclosure. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. The EPSS score is approximately 0.177%, reflecting a low probability of exploitation in the near term. The high attack complexity further reduces practical exploitability, as attackers must meet specific conditions to trigger the faulty compiler comparison (Oracle CPU Oct 2026, Red Hat Bugzilla).

Minderung und Workarounds

Oracle has released patches for this vulnerability as part of the October 2026 Critical Patch Update. Users should upgrade to the next available patched release for their Java SE version (e.g., the subsequent quarterly CPU release beyond the affected versions listed). Red Hat has addressed this issue via errata RHSA-2026:88347 (RHEL 9/10), RHSA-2026:88352 (RHEL 8 variants), RHSA-2026:88353 (OpenJDK 17.0.21), and RHSA-2026:89916 (Red Hat Build of OpenJDK 17.0.20.1). As a temporary workaround, Oracle recommends restricting network access to Java applications and APIs where possible, and implementing network segmentation to limit exposure of systems running affected Java SE versions (Oracle CPU Oct 2026, Red Hat Bugzilla).

Reaktionen der Community

Red Hat promptly issued multiple security errata addressing CVE-2026-91487 across RHEL 8, RHEL 9, RHEL 10, and Red Hat Build of OpenJDK within one week of Oracle's disclosure, indicating active downstream patching activity. No notable independent researcher commentary or significant social media discussion has been identified for this medium-severity vulnerability (Red Hat Bugzilla).

Zusätzliche Ressourcen

Status der Linux-Distribution-Korrektur

Beheben Sie die Verfügbarkeit in großen Linux-Distributionen und deren Veröffentlichungen.

Debian

Behoben

bookworm

openjdk-17: 17.0.21+9-1~deb12u1

Behoben

sid

openjdk-8

Betroffen

trixie

openjdk-25: 25.0.5+8-1~deb13u1

Behoben

Ubuntu

Unbekannt

bionic (esm-apps)

openjdk-8

Unbekannt

bionic (esm-infra)

openjdk-lts

Unbekannt

devel

openjdk-8

Unbekannt

focal (esm-apps)

openjdk-8

Unbekannt

focal (esm-infra)

openjdk-lts

Unbekannt

jammy

openjdk-8

Unbekannt

jammy (esm-apps)

openjdk-8

Unbekannt

noble

openjdk-8

Unbekannt

RHEL / CentOS

Behoben

RHEL 8

:appstream:java-17-openjdk-1:17-openjdk-17.0.21.0.9-2.1.el8.src

Behoben

RHEL 9

:appstream:java-25-openjdk-1:25-openjdk-25.0.5.0.8-1.0.el9.src

Behoben

RHEL 10

java-25-openjdk-1:25-openjdk-25.0.5.0.8-1.0.el10.src

Behoben

Alpine

Behoben

edge

openjdk21: 21.0.13.0.3_p1-r0, 25.0.5.0.3_p1-r0

Behoben

v3.23

openjdk21: 21.0.13.0.3_p1-r0, 25.0.5.0.3_p1-r0

Behoben

Quelle: Dieser Bericht wurde mit KI erstellt

Verwandte Themen Amazon Corretto JDK Schwachstellen:

CVE-ID

Schwere

Punktzahl

Technologieen

Bauteilname

CISA KEV-Exploit

Hat Lösung

Veröffentlichungsdatum

CVE-2026-114820CRITICAL9.1
  • Amazon Corretto JDK logoAmazon Corretto JDK
  • java-17-openjdk-src-fastdebug
NeinJaOct 24, 2026
CVE-2026-91403CRITICAL9.1
  • Amazon Corretto JDK logoAmazon Corretto JDK
  • java-17-openjdk-devel-fastdebug
NeinJaOct 21, 2026
CVE-2026-111943MEDIUM6.8
  • Go logoGo
  • kong-ingress-controller-fips
NeinJaOct 21, 2026
CVE-2026-91464MEDIUM5.3
  • Amazon Corretto JDK logoAmazon Corretto JDK
  • java-21-ibm-semeru-certified-jdk-headless
NeinJaOct 20, 2026
CVE-2026-91487MEDIUM4.8
  • Amazon Corretto JDK logoAmazon Corretto JDK
  • java-1.8.0-openjdk-src-debug
NeinJaOct 20, 2026

Kostenlose Verwundbarkeitsbewertung

Benchmark für Ihre Cloud-Sicherheitslage

Bewerten Sie Ihre Cloudsicherheitspraktiken in 9 Sicherheitsbereichen, um Ihr Risikoniveau zu bewerten und Schwachstellen in Ihren Verteidigungen zu identifizieren.

Anforderungsbewertung

Zusätzliche Wiz-Ressourcen

Eine personalisierte Demo anfordern

Sind Sie bereit, Wiz in Aktion zu sehen?

"Die beste Benutzererfahrung, die ich je gesehen habe, bietet vollständige Transparenz für Cloud-Workloads."
David EstlickCISO
"„Wiz bietet eine zentrale Oberfläche, um zu sehen, was in unseren Cloud-Umgebungen vor sich geht.“ "
Adam FletcherSicherheitsbeauftragter
"„Wir wissen, dass, wenn Wiz etwas als kritisch identifiziert, es auch wirklich kritisch ist.“"
Greg PoniatowskiLeiter Bedrohungs- und Schwachstellenmanagement