CVE-2025-50069
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 · uneditedVulnerability in the Java VM component of Oracle Database Server. Supported versions that are affected are 19.3-19.27 and 21.3-21.18. Easily exploitable vulnerability allows low privileged attacker having Create Session, Create Procedure privilege with network access via Oracle Net to compromise Java VM. While the vulnerability is in Java VM, attacks may significantly impact additional products (scope change). 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.7 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 confidenceVulnerability in Oracle Database Server's Java VM component allows low-privileged attackers with Create Session and Create Procedure privileges to gain unauthorized access to sensitive data via network. The scope change indicates the attack can impact additional products beyond Java VM.
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>= 19.3, <= 19.27>= 21.3, <= 21.18CVSS 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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Oracle Java VM component is installedQuery Oracle data dictionary views such as DBA_REGISTRY or ALL_OBJECTS to verify the presence of the Java VM component in the databaseAffected if Java VM is not present in the database inventory
-
Identify the Oracle Database versionExecute SELECT VERSION FROM V$INSTANCE or check the banner from CONNECT / AS SYSDBA to retrieve the installed database versionAffected if The version falls within 19.3 to 19.27 or 21.3 to 21.18
-
Verify Java VM is enabled and accessibleCheck if Java VM component status is VALID in DBA_REGISTRY and attempt a simple Java execution test or query the Java$* viewsAffected if Java VM is loaded and accessible to database users
-
Audit users with Create Session privilegeQuery DBA_SYS_PRIVS or USER_SYS_PRIVS for users granted CREATE SESSION system privilegeAffected if Any non-admin user has Create Session privilege
-
Audit users with Create Procedure privilegeQuery DBA_SYS_PRIVS for users granted CREATE PROCEDURE privilegeAffected if Any non-admin user has Create Procedure privilege
A user is affected if their Oracle Database runs a version between 19.3-19.27 or 21.3-21.18, has Java VM installed and enabled, and contains users with both Create Session and Create Procedure privileges accessible to low-privileged attackers.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply the Oracle Critical Patch Update (CPU) containing the fix for this vulnerability. If immediate patching is not feasible, restrict network access to Oracle Net and limit Create Session/Create Procedure privileges to essential users only.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-50069 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-50069 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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