Access ManagerApplication · Oracle

CVE-2026-47037

HIGH · 8.8 CVSS v3.1 Published 2026-07-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Access Manager product of Oracle Fusion Middleware (component: Authentication Engine). The supported version that is affected is 14.1.2.1.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Access Manager. Successful attacks of this vulnerability can result in takeover of Oracle Access Manager. 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

A vulnerability in the Authentication Engine of Oracle Access Manager (version 14.1.2.1.0) allows low-privileged attackers with network access via HTTP to bypass authentication controls and gain complete administrative control of the OAM system, resulting in full confidentiality, integrity, and availability compromise.

MitigationApply the Oracle Critical Patch Update for Oracle Access Manager 14.1.2.1.0 immediately. Until patch deployment, restrict network access to OAM administrative interfaces and implement additional access controls on upstream proxies.

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
Access ManagerApplication
Affected:= 14.1.2.1.0

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. Identify Oracle Access Manager installation
    Check for Oracle Access Manager components on the system. Common installation paths include $ORACLE_HOME/oam or /u01/app/oracle/products/14.1.2.1.0/oam. Look for the Authentication Engine component directory structure.
    Affected if Oracle Access Manager is not installed on the system, the vulnerability does not apply.
  2. Verify Authentication Engine version
    Locate the Authentication Engine component version file or check the OAM console for component versions. Common methods: grep for '14.1.2.1.0' in OAM installation directories, or query the OAM administration console for component version information.
    Affected if The Authentication Engine version is exactly 14.1.2.1.0 - this specific version is affected.
  3. Confirm network accessibility of Authentication Engine
    Check if the OAM Authentication Engine endpoints are exposed to the network. Review web server or load balancer configurations for rules exposing the OAM login and authentication URLs. Test connectivity to typical OAM auth endpoints on ports 7001, 8001, or configured HTTP ports.
    Affected if The Authentication Engine interface is reachable via network HTTP/HTTPS - this is required for remote exploitation.
  4. Check authentication engine configuration
    Review OAM configuration files in the oam_domain/config directory for authentication pipeline settings. Look for the authentication engine configuration that handles SQL-based operations.
    Affected if The SQL injection flaw exists within the Authentication Engine component's SQL handling logic in version 14.1.2.1.0.

You are affected only if Oracle Access Manager with Authentication Engine version 14.1.2.1.0 is installed AND the Authentication Engine interface is network-accessible via HTTP.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Oracle Critical Patch Update for Oracle Access Manager 14.1.2.1.0 immediately. Until patch deployment, restrict network access to OAM administrative interfaces and implement additional access controls on upstream proxies.

Fix this in Access Manager Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing16.0 h
  • Review / QA8.0 h
48.0 hours of engineering $8,320
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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