Introduction
According to Oracle's November 2026 Critical Security Patch Update, an unauthenticated attacker who can reach Oracle Access Manager over TCP can make the service hang or crash repeatedly. Access Manager is the component that authenticates users, validates tokens, and creates sessions on behalf of the applications behind it. A complete outage of its Authentication Engine therefore affects every application that delegates sign-on to it.
Oracle Access Manager (OAM) is the access management product within Oracle Fusion Middleware. It provides single sign-on and multifactor authentication across cloud and on-premises systems, and applications hand off authentication and authorization to it through registered agents. It is an established product in the access management category. Gartner Peer Insights maintains an Oracle Access Management profile, and QKS Group covers Oracle in its access management market study. Public material does not, however, establish a specific market share or ranking.
The issue is tracked as CVE-2026-91516, with an Oracle-assigned CVSS 3.1 base score of 7.5. This post summarizes what Oracle and secondary trackers have published: what is known about the flaw, what is not, and how the fix is delivered.
Technical Information
What Oracle disclosed
Oracle's description is short and specific about conditions and outcome, and silent on mechanics:
- Product: Oracle Access Manager, part of Oracle Fusion Middleware
- Component: Authentication Engine
- Protocol: TCP
- Authentication required: None. Oracle marks it remotely exploitable without authentication.
- Exploitability: Oracle calls it "easily exploitable"
- Impact: "unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle Access Manager"
The published vector is:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Here is what each metric means under the FIRST CVSS v3.1 definitions:
- AV:N (Network): exploitable over a network. Oracle specifies TCP. FIRST notes that Network also covers attacks only possible from an intranet, so this does not by itself imply internet exposure.
- AC:L (Low): no special conditions are required.
- PR:N (None): no account or prior privileges.
- UI:N (None): no victim action required.
- S:U (Unchanged): impact stays within the same security authority.
- C:N / I:N: no confidentiality or integrity impact is assigned. Nothing disclosed points to data exposure or code execution.
- A:H (High): complete loss of availability of Oracle Access Manager.
The CVSS base score measures intrinsic severity. On its own, it says nothing about whether attacks are occurring or whether exploit code exists.
Root cause: what is and is not known
Oracle Access Manager is closed source. There is no public commit, diff, or changelog, and Oracle has not disclosed:
- a destination port or listener
- a packet or message format
- the vulnerable function or code path
- a request sequence or required traffic volume
- any memory corruption primitive
The weakness classification also varies by source. The CVE record from Oracle lists no CWE. NVD now displays CWE-400 (Uncontrolled Resource Consumption), attributed to the CISA ADP enrichment. VulDB assigns CWE-404 instead. These are third-party classifications, not a demonstrated root cause.
If you read CWE-400 alongside Oracle's hang or crash wording, the most plausible interpretation is that the fix adds limits or validation to how the Authentication Engine handles untrusted TCP input, so a remote client can no longer exhaust it. Oracle has not confirmed this and no code is available to check it against, so treat it as an inference rather than a finding. The confirmed technical fact is narrower: unauthenticated TCP access to the Authentication Engine can produce a complete denial of service.
Attack flow
Based only on what Oracle published, the attack looks like this at a high level:
- The attacker has network reachability over TCP to the Oracle Access Manager Authentication Engine. This may be from the internet or from an internal network, depending on deployment.
- No credentials, session, or user interaction are needed.
- The attacker sends traffic that the Authentication Engine mishandles. Its content and structure are undisclosed.
- Oracle Access Manager hangs or crashes. Oracle describes the crash as "frequently repeatable", so an attacker could plausibly trigger it again after the service restarts.
We deliberately go no further than this. The phrase "easily exploitable" describes the CVSS attack complexity rating, not an exploit recipe.
Why an availability-only flaw still matters here
Oracle's documentation describes Access Manager as the place where applications delegate authentication and authorization through registered agents, and where authentication, token validation, and session creation happen. When the Authentication Engine is unavailable, those functions are unavailable to dependent applications. Neither Oracle nor any other source quantifies outage duration or the number of affected downstream applications.
Exploitation status
- In the wild: not established in any reviewed source. No threat actor or campaign has been named.
- Public exploit or PoC: Rapid7 lists no exploit module or proof of concept. VulDB reports technical details as unknown and no exploit available. Neither rules out private exploit development.
- CISA KEV: Rapid7 marks the CVE as not in the KEV catalog.
- EPSS: Rapid7 lists the score and percentile as unavailable.
So high exploitability is documented, but active exploitation is not.
Patch Information
Oracle fixed CVE-2026-91516 in its November 2026 Critical Security Patch Update (CSPU), released November 17, 2026. The fix covers both affected release lines, 12.2.1.4.0 and 14.1.2.1.0. The only public evidence of the fix is Oracle's advisory, its risk matrix, and the CVE record that links to them.
Obtaining the patch
The advisory does not link to a single downloadable file. Its Patch Availability table sends Fusion Middleware customers to My Oracle Support Document CPU450 (Fusion Middleware), which has per-release patch numbers and installation steps. A few constraints apply:
- Downloading requires a valid Oracle support contract. The public CPU450 link leads to a sign-in page, so patch IDs and prerequisites are not publicly visible.
- Oracle only provides CSPU patches for versions under Premier or Extended Support.
- Oracle notes that older, unsupported releases are not tested and are "likely" affected as well. If you run an unsupported OAM version, upgrade to 12.2.1.4.0 or 14.1.2.1.0 before patching. Don't assume a release is safe just because it isn't listed.
- If you have skipped earlier security patches, Oracle points you to earlier advisories to work out the correct sequence.
CSPU versus quarterly CPU
CSPUs are Oracle's new monthly releases outside the quarterly cycle. Oracle describes them as targeted, high-priority fixes that "complement Oracle's existing quarterly cumulative Critical Patch Updates (CPUs)." In practice:
- This fix ships as a focused CSPU patch and is not part of the October 2026 CPU. Applying the October CPU alone leaves CVE-2026-91516 unfixed.
- Track it as a separate patch item until a later quarterly CPU confirms it has been included.
Other OAM fixes in the same CSPU
The November CSPU also fixes many other Oracle Access Manager vulnerabilities, most of them in the same Authentication Engine component, including:
- CVE-2026-91500, CVE-2026-91510, and CVE-2026-91507 (CVSS 9.3 to 10.0, HTTP)
- SAML-reachable issues such as CVE-2026-91498, CVE-2026-91509, and CVE-2026-91522
- Another TCP-reachable flaw, CVE-2026-91543
- A 10.0-rated Admin Console flaw, CVE-2026-114835
If you are patching OAM for CVE-2026-91516, apply everything in the November CSPU for OAM rather than isolating this one fix.
Temporary risk reduction
Oracle's advisory says that blocking the network protocols an attack requires may reduce risk until patches are applied. For this CVE, the protocol is identified only as TCP, and Oracle supplies no port or targeted rule. Oracle states explicitly that such restrictions do not correct the underlying problem, are not long-term solutions, may break application functionality, and should be tested on nonproduction systems first. Oracle's generic privilege restriction advice does not apply here, because the vector requires no privileges.
Tracker discrepancies
Some aggregators listed this CVE as "No fix available yet" right after publication, and NVD still shows the entry with status "Received" and no independent analysis. Treat both as sync lag. Oracle's advisory and risk matrix confirm the fix shipped on November 17, 2026.
Affected Systems and Versions
- Product: Oracle Access Manager (Oracle Fusion Middleware)
- Component: Authentication Engine
- Affected supported versions: 12.2.1.4.0 and 14.1.2.1.0
- Vulnerable configuration: any affected deployment where an unauthenticated attacker has TCP network reachability to the Authentication Engine. No additional configuration preconditions are disclosed.
- Unsupported releases: not tested by Oracle and described as likely affected. They do not receive CSPU patches.
Vendor Security History
Oracle describes its Oracle Software Security Assurance (OSSA) program as a lifecycle methodology covering design, build, testing, and maintenance, with secure coding standards, mandatory security training, security leadership within development groups, and automated analysis and testing. These are process commitments made by Oracle, not independent evidence about defect rates.
The most relevant precedent is CVE-2021-35587, a different Oracle Access Manager vulnerability with an unauthenticated, HTTP-based takeover impact:
- Oracle patched it in January 2022.
- A public proof of concept followed in March 2022.
- CISA added it to the Known Exploited Vulnerabilities catalog on November 28, 2022. Its required action is to apply updates per vendor instructions, and its ransomware campaign field is "Unknown".
- The Record reported that GreyNoise observed attacks from November 29 onward while vulnerable, internet-exposed systems remained.
That case shows the gap between a patch being available and exposure being eliminated. It does not imply anything about exploitation of CVE-2026-91516, which differs in protocol (TCP versus HTTP) and in impact (denial of service versus takeover). Oracle's November 2026 advisory makes a related general point: it continues to receive reports of attacks against vulnerabilities that were already patched, some of which succeeded against customers who had not applied the fixes.
References
- NVD: CVE-2026-91516
- CVE Record: CVE-2026-91516
- Oracle Critical Security Patch Update Advisory, November 2026
- Text Form of Oracle CSPU November 2026 Risk Matrices
- CIRCL Vulnerability Lookup: CVE-2026-91516
- My Oracle Support Document CPU450 (sign in required)
- VulDB: Oracle Access Manager Authentication denial of service
- Rapid7 Vulnerability Database: CVE-2026-91516
- TheHackerWire: CVE-2026-91516 Exploit Status and Fix
- FIRST CVSS v3.1 Specification Document
- Oracle Docs: Understanding Single Sign On with Access Manager
- Oracle Access Management product page
- Oracle Software Security Assurance
- About Oracle
- CISA KEV entry for CVE-2021-35587
- CISA Known Exploited Vulnerabilities Catalog
- CISA KEV JSON feed
- The Record: More than 150 Oracle Access Management systems exposed to bug highlighted by CISA
- Gartner Peer Insights: Oracle Access Management
- QKS Group: Market Share, Access Management, 2025, Worldwide



