dbcve.org
Applications DbaApplication · Oracle

CVE-2026-61110

HIGH · 8.8 CVSS v3.1 Published 2026-07-21
Fix available
A fix is available. Upgrade to after 12.2.15 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click 4 weeks old

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 Oracle Applications DBA product of Oracle E-Business Suite (component: ADPatch). Supported versions that are affected are 12.2.3-12.2.15. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Applications DBA. Successful attacks of this vulnerability can result in takeover of Oracle Applications DBA. CVSS 3.1 Base Score 8.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

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 Oracle Applications DBA ADPatch component allows a low-privileged attacker with network access via HTTP to achieve complete takeover of the Oracle Applications DBA system. The vulnerability affects Oracle E-Business Suite versions 12.2.3 through 12.2.15, with all three security pillars (Confidentiality, Integrity, Availability) impacted at High severity.

MitigationApply the latest Oracle Critical Patch Update (CPU) for Oracle E-Business Suite that addresses this vulnerability in the ADPatch component. Restrict network access to ADPatch administration interfaces and follow the principle of least privilege for user accounts.

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
Applications DbaApplication
Affected:>= 12.2.3, <= 12.2.15

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Verify Oracle E-Business Suite installation
    Locate the E-Business Suite installation directory (commonly $ORACLE_HOME/apps or in Windows check for Oracle Applications DBA installation paths) or query running services for Oracle EBS components
    Affected if Oracle E-Business Suite is installed and running
  2. Identify Oracle Applications DBA version
    Query the version using Oracle's AD utilities: run 'ad Identification' or check the version.txt file in $APPL_TOP/admin or the apps 数据库 (select release_name from apps.fnd_product_groups)
    Affected if Version falls within 12.2.3 through 12.2.15 inclusive
  3. Confirm ADPatch component is present
    Check for the ADPatch executable in $AD_TOP/bin or the presence of ADPatch web interfaces in the Oracle Applications Manager (OAM) console
    Affected if ADPatch component is installed and available in the environment
  4. Assess ADPatch network accessibility
    Determine if HTTP-accessible interfaces to ADPatch are exposed by reviewing Oracle E-Business Suite web listener configuration (check Oracle HTTP Server or Oracle Application Server settings for ADPatch-related endpoints)
    Affected if ADPatch interfaces are reachable over HTTP/HTTPS from network locations accessible to low-privileged users

If Oracle Applications DBA version is 12.2.3 through 12.2.15 and ADPatch is accessible via HTTP, the environment is affected by this vulnerability.

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 12.2.15
Interim mitigation

Apply the latest Oracle Critical Patch Update (CPU) for Oracle E-Business Suite that addresses this vulnerability in the ADPatch component. Restrict network access to ADPatch administration interfaces and follow the principle of least privilege for user accounts.

Recommended fix Moderate confidence

Apply Oracle Critical Patch Update (CPU) patch for Oracle E-Business Suite 12.2.x

  1. 1. Access Oracle Critical Patch Update advisories at https://www.oracle.com/security-alerts/
  2. 2. Locate the Oracle E-Business Suite Critical Patch Update for the applicable quarter that addresses CVE-2026-61110
  3. 3. Download the corresponding security patch for Oracle Applications DBA (ADPatch component) from Oracle Support
  4. 4. Review the patch readme and prerequisites documentation
  5. 5. Apply the patch following Oracle's standard ADPatch application procedures
  6. 6. Verify the patch was applied successfully using AD Administration utility or querying FND_PRODUCT_PATCHES table
  7. 7. Test critical ADPatch functionality to ensure normal operations
Caveat Oracle CPU patches are cumulative; ensure all prerequisites are met before applying

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

Fix this in Applications Dba Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-61110 — 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-61110 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