Low Info disclosure

CVE-2026-34268 — Exposure of Sensitive Information in Oracle Graalvm

Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Security). Supported versions that are affected are Oracle Java SE: 8u481, 8u481-b50, 8u481-perf, 11.0.30, 17.0.18, 21.0.10, 25.0.2, 26; Oracle GraalVM for JDK: 17.0.18 and 21.0.10; Oracle GraalVM Enterprise Edition: 21.3.17. Difficult to exploit vulnerability allows unauthenticated attacker with logon to the infrastructure where Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition executes to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability can be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. This vulnerability also applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. CVSS 3.1 Base Score 2.9 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N).

Published Apr 21, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: oracle

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.1% (30-day exploitation probability)+1

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.15%

ahead of 3% of scored CVEs · Oct 14, 2026

Affects

Oracle

Graalvm and 5 more

CVSS base

2.9

Low · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Oracle Graalvm, Oracle Graalvm For Jdk, Oracle Java Se…).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes matching the vulnerability class (info disclosure), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Oracle	Graalvm	version 21.3.17	Vulnerable	NIST National Vulnerability Database
Oracle	Graalvm For Jdk	version 21.0.10version 17.0.18	Vulnerable	CVE Program (cve.org) e CISA ADP
Oracle	Graalvm For Jdk	version 21.0.10version 17.0.18	Vulnerable	NIST National Vulnerability Database
Oracle	Java Se	version 17.0.18version 11.0.30version 8u481-perfversion 8u481-b50version 8u481version 21.0.10version 25.0.2version 26	Vulnerable	CVE Program (cve.org) e CISA ADP
Oracle	Jdk	version 26version 25.0.2version 1.8.0-update481version 21.0.10version 17.0.18version 11.0.30version 1.8.0-update481_b50	Vulnerable	NIST National Vulnerability Database
Oracle	Jre	version 26version 25.0.2version 21.0.10version 17.0.18version 11.0.30version 1.8.0-update481_b50version 1.8.0-update481	Vulnerable	NIST National Vulnerability Database
Oracle	Oracle GraalVM Enterprise Edition	version 21.3.17	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Local

Attack complexity

High

Privileges required

None

User interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
2.9	CVSS 3.1	Low	1.4	1.4	secalert_us@oracle.com via NIST National Vulnerability Database
2.9	CVSS 3.1	Low	—	—	oracle via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N (score shown at the top: secalert_us@oracle.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-200 · Exposure of Sensitive Information

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.15%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Look for anomalous data read/export volumes and access to sensitive records.

endpoint telemetry (EDR)application logsauthentication logs

Timeline

What happened to this CVE, newest first.

2026
Affected products added · oracle corporation/oracle java se, oracle corporation/oracle graalvm for jdk, oracle corporation/oracle graalvm enterpri
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
CVSS changed · 2.9
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
CVE published
Apr 21, 2026 · oracle

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

1 on the record

www.oracle.com/security-alerts/cpuapr2026.html
Vendor Advisory, vendor-advisory, NIST National Vulnerability Database

Elsewhere on this site

Oracle
every CVE for this vendor

Info disclosure
same class

CWE-200
other pages naming this weakness

Related CVEs (same products)

High CVE-2026-62574 Improper Access Control in Oracle Jre Jul 21, 2026
Medium CVE-2026-60526 Improper Input Validation in Oracle Jdk Jul 21, 2026
Low CVE-2026-60166 Vulnerability in Oracle Java SE (component: JavaFX). The supported version that is… Jul 21, 2026
Low CVE-2026-60164 Vulnerability in Oracle Java SE (component: JavaFX). The supported version that is… Jul 21, 2026
Medium CVE-2026-60147 Improper Access Control in Oracle Jre Jul 21, 2026
High CVE-2026-47063 Improper Access Control in Oracle Jre Jul 21, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-34268 is "Exposure of Sensitive Information in Oracle Graalvm", rated Low. It affects Graalvm (Oracle); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 2.9 describes technical severity. EPSS 0.15% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.