CVE-2026-61065: Vulnerability in the Oracle Access Manager product of Oracle Fusion Middleware (component: Authentication E...
Vulnerability in the Oracle Access Manager product of Oracle Fusion Middleware (component: Authentication Engine). Supported versions that are affected are 12.2.1.4.0 and 14.1.2.1.0. Easily exploitable vulnerability allows unauthenticated 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 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
Security readout for executives and security teams
Plain-English summary
A remote, unauthenticated attacker who can reach a vulnerable Oracle Access Manager service over HTTP may take complete control of it. Because Access Manager protects authentication and access, compromise could expose sensitive information, alter security controls, disrupt availability, and undermine trust in connected applications.
Executive priority
Treat this as an immediate identity-security priority. Establish affected-system ownership, exposure, and remediation status now. Internet-facing or broadly reachable instances should receive the fastest attention because compromise could affect Access Manager and the applications relying on it. Escalate any unexplained administrative or authentication activity for incident investigation.
Technical view
CVE-2026-61065 is an authentication weakness, classified as CWE-287, in Oracle Access Manager’s Authentication Engine. Versions 12.2.1.4.0 and 14.1.2.1.0 are affected. The network-reachable flaw requires neither privileges nor user interaction and may cause high confidentiality, integrity, and availability impact. CVSS 3.1: 9.8.
Likely exposure
Exposure is highest where affected Oracle Access Manager versions accept HTTP traffic from untrusted or broadly accessible networks. The supplied evidence does not identify affected configurations, listening paths, deployment prerequisites, or whether internet exposure is required. Organizations must verify product versions and network reachability directly.
Exploitation context
The source bundle marks this CVE as absent from KEV and provides no cited evidence of active exploitation. However, Oracle describes it as easily exploitable, unauthenticated, and capable of product takeover. Treat exploitation status as unconfirmed rather than assuming attacks are occurring or absent.
Researcher notes
The supplied record identifies the Authentication Engine and CWE-287 but provides no root-cause detail, affected endpoint, proof of concept, exploitation telemetry, or confirmed fixed versions. Avoid inferring implementation specifics. Research should focus defensively on version confirmation, HTTP reachability, update verification, and indicators across Access Manager and dependent identity systems.
Mitigation direction
Inventory Oracle Access Manager deployments and identify installations running either affected version.
Review Oracle’s July 2026 advisory for official patches, prerequisites, and installation guidance.
Apply Oracle-provided remediation under an expedited, tested change process.
Restrict HTTP access to trusted networks while remediation is pending.
Monitor Access Manager and connected identity systems for suspicious authentication or configuration activity.
Validation and detection
Confirm deployed Oracle Access Manager versions using authoritative asset and configuration records.
Test whether affected services are reachable over HTTP from untrusted network segments.
Verify Oracle’s prescribed update is installed successfully on every affected instance.
Review authentication, administrative, and configuration logs for unexplained activity.
Retest network exposure and identity workflows after remediation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-287: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-287 · source CWE mapping
Improper Authentication
Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.