dbcve.org
Java Virtual MachineApplication · Oracle

CVE-2026-35229

HIGH · 7.5 CVSS v3.1 Published 2026-04-21
Fix available
A fix is available. Upgrade to after 21.21 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vulnerability in the Java VM component of Oracle Database Server. Supported versions that are affected are 19.3-19.30 and 21.3-21.21. Easily exploitable vulnerability allows unauthenticated attacker with network access via Oracle Net to compromise Java VM. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Java VM accessible data. CVSS 3.1 Base Score 7.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Vulnerability in the Java VM component of Oracle Database Server affecting versions 19.3-19.30 and 21.3-21.21. Easily exploitable via network access through Oracle Net without authentication, allowing unauthorized access to critical data or complete access to all Java VM accessible data. CVSS 3.1 base score 7.5 reflects high confidentiality impact with no integrity or availability compromise.

MitigationApply the corresponding Oracle Critical Patch Update (CPU) for this vulnerability to the affected Oracle Database instances, or upgrade to a patched version. Restrict network access to Oracle Net listeners as an additional compensating control.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Java Virtual MachineApplication
Affected:>= 19.3, <= 19.30>= 21.3, <= 21.21

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Oracle Database version
    Connect to the database as a privileged user (e.g., SYS or SYSTEM) and run: SELECT VERSION FROM V$INSTANCE; or SELECT BANNER FROM V$VERSION WHERE BANNER LIKE 'Oracle Database%'; Compare the returned version against the affected ranges 19.3-19.30 and 21.3-21.21.
    Affected if The installed version falls within 19.3 to 19.30, or 21.3 to 21.21.
  2. Verify Java VM component is installed
    Query the Oracle component registry: SELECT COMP_NAME, VERSION, STATUS FROM DBA_REGISTRY WHERE COMP_NAME LIKE '%Java%'; or check V$OPTION to see if Java is enabled: SELECT PARAMETER, VALUE FROM V$OPTION WHERE PARAMETER = 'Java';
    Affected if Java VM shows as INSTALLED or VALID in the registry.
  3. Confirm Java VM is actually in use
    Check for any Java objects, classes, or resources in the database: SELECT OWNER, OBJECT_NAME, OBJECT_TYPE FROM DBA_OBJECTS WHERE OBJECT_TYPE LIKE '%JAVA%' FETCH FIRST 10 ROWS ONLY; Or check for Java schemas: SELECT USERNAME FROM DBA_USERS WHERE USERNAME LIKE '%JAVA%';
    Affected if Any Java objects, schemas, or resources exist in the database.
  4. Assess Oracle Net listener exposure
    Check the listener configuration by running: lsnrctl status LISTENER (or the configured listener name). Verify the HOST binding and port (typically 1521). Determine if the listener is bound to 0.0.0.0 (all interfaces) or a public IP address accessible from untrusted networks.
    Affected if The Oracle Net listener is accessible from network addresses outside the trusted environment.

A user is affected if their Oracle Database version is 19.3-19.30 or 21.3-21.21, the Java VM component is installed, and the Oracle Net listener is network-accessible without additional filtering.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 21.21
Interim mitigation

Apply the corresponding Oracle Critical Patch Update (CPU) for this vulnerability to the affected Oracle Database instances, or upgrade to a patched version. Restrict network access to Oracle Net listeners as an additional compensating control.

Recommended fix High confidence

Upgrade to Oracle Database 19.31+ or 21.22+ (or apply the relevant security patch)

  1. Identify the current Oracle Database version by querying SELECT VERSION FROM V$INSTANCE;
  2. Confirm the version falls within the affected range: 19.3-19.30 or 21.3-21.21
  3. Schedule a maintenance window for the upgrade process
  4. Download the latest Oracle Database PSU (Patch Set Update) for your version from Oracle Support (My Oracle Support)
  5. Apply the security patch following Oracle's standard patching documentation
  6. Alternatively, upgrade to the next available Oracle Database release: 19.31 or later for the 19c line, or 21.22 or later for the 21c line
  7. After patching/upgrade, verify the Java VM component version matches the patched release using dbms_java version queries
  8. Restrict network access to Oracle Net listener (Oracle Net) using firewall rules or Oracle Net configuration to limit exposure
Caveat Standard Oracle Database upgrade considerations apply: test in staging environment, review Oracle's upgrade documentation for potential incompatibilities, ensure backup before upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Java Virtual Machine Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-35229 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-35229 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data