Applications DbaApplication · Oracle

CVE-2026-22011

HIGH · 7.6 CVSS v3.1 Published 2026-04-21
Fix available
A fix is available. Upgrade to after 12.2.15 or later.
See remediation →
80/100
Remediation priority · High
Remotely reachable

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. Difficult to exploit vulnerability allows high privileged attacker with network access via HTTP to compromise Oracle Applications DBA. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Applications DBA, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle Applications DBA. CVSS 3.1 Base Score 7.6 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/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 · moderate confidence

Vulnerability in Oracle Applications DBA's ADPatch component (versions 12.2.3-12.2.15) allowing high-privileged attackers with network access via HTTP to achieve takeover. Exploitation requires human interaction and demonstrates scope change, potentially affecting additional products beyond Oracle Applications DBA.

MitigationApply Oracle's latest patch for the affected E-Business Suite versions (12.2.3-12.2.15). Limit high-privileged account access and network exposure of the ADPatch interface until patching is completed.

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
High
Privileges
High
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/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. Identify ADPatch component version
    Locate the ADPatch utility in your Oracle Applications DBA installation and run the version check command (commonly 'adpatch -version' or inspect the version file in the AD_TOP directory)
    Affected if The reported version falls within 12.2.3 through 12.2.15 inclusive
  2. Confirm Oracle E-Business Suite version
    Query the Oracle database or check the installation directory for the E-Business Suite version using 'adident Header adpatch' or review the version referenced in the APPL_TOP
    Affected if The E-Business Suite version is between 12.2.3 and 12.2.15
  3. Determine if ADPatch HTTP interface is network-accessible
    Review your web server or Oracle HTTP Server configuration to check if the ADPatch endpoint is exposed over HTTP/HTTPS to the network
    Affected if The ADPatch interface is reachable via HTTP from network locations outside the trusted administration zone
  4. Verify high-privileged account exposure
    Review access controls and authentication configuration for the ADPatch HTTP interface to determine if high-privileged attacker access is possible
    Affected if High-privileged Oracle application accounts can authenticate to the exposed ADPatch HTTP interface

Your environment is affected if Oracle Applications DBA ADPatch version is 12.2.3-12.2.15 AND the HTTP interface is network-accessible with high-privileged account authentication enabled.

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.

From vendor data
Upgrade available Upgrade to a release after 12.2.15
Interim mitigation

Apply Oracle's latest patch for the affected E-Business Suite versions (12.2.3-12.2.15). Limit high-privileged account access and network exposure of the ADPatch interface until patching is completed.

Fix this in Applications Dba Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
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,192.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22011 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