CVE-2025-61881
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.28, 21.3-21.19 and 23.4-23.9. Difficult to exploit vulnerability allows unauthenticated attacker with network access via Oracle Net to compromise Java VM. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Java VM accessible data. CVSS 3.1 Base Score 5.9 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/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's Java VM component allows unauthenticated attackers with network access via Oracle Net to create, delete, or modify data within the Java VM environment. The attack is characterized as difficult to exploit, requiring high-complexity attack vectors (CVSS AC:H), but requires no authentication (PR:N).
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.28>= 21.3, <= 21.19>= 23.4, <= 23.9CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/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.
-
Identify the Oracle Database versionConnect to the database as SYSDBA and run: SELECT version FROM v$instance; or check the Oracle inventory for the installed database version.Affected if The version falls within 19.3-19.28, 21.3-21.19, or 23.4-23.9.
-
Determine if Java VM is installedQuery the database as SYSDBA: SELECT comp_name, version, status FROM dba_registry WHERE comp_name LIKE '%Java%';Affected if Java VM appears in the registry with a status of VALID or LOADED.
-
Check if Java VM is actually present in the databaseQuery as SYSDBA: SELECT owner, object_name FROM dba_objects WHERE object_type='JAVA CLASS' AND ROWNUM <= 10; or check for the presence of the JAVAVM subsystem.Affected if Java classes or the JAVAVM subsystem exists in the database.
-
Verify Oracle Net is accessibleCheck listener.ora and sqlnet.ora configuration files for listener binding, and test network connectivity to the Oracle Net port (typically 1521) from untrusted networks.Affected if Oracle Net listener accepts remote connections from networks accessible to unauthenticated attackers.
The environment is affected if the Oracle Database version is within the listed ranges AND Java VM is installed/present AND the Oracle Net listener is network-accessible to unauthenticated 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 Oracle Critical Patch Updates for the affected versions (19.3-19.28, 21.3-21.19, 23.4-23.9). Additionally, restrict network access to Oracle Net ports and consider disabling Java VM if not required in the database environment.
- Consultation4.0 h
- Implementation6.0 h
- Testing8.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 $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-61881 — 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-61881 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