Security readout for executives and security teams
Plain-English summary
A low-privileged attacker who can reach an affected Oracle Identity Manager Connector over TLS could take control without user interaction. Successful compromise may expose or alter sensitive identity-management data, disrupt availability, and affect connected products. The severity is critical because exploitation is described as easy and the impact extends beyond the vulnerable component.
Executive priority
Prioritize immediate identification and remediation of affected instances, especially those reachable from broad networks or linked to sensitive identity systems. Require owners to document version, reachability, remediation status, and evidence of validation. Escalate suspected compromise to incident response because successful exploitation may affect connected products.
Technical view
CVE-2026-60990 is an authorization weakness, classified as CWE-284, affecting Oracle Identity Manager Connector 12.2.1.4.0 and 14.1.2.1.0. The CVSS 3.1 score is 9.9: network-accessible, low complexity, low privileges, no user interaction, changed scope, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to the two named supported versions where an attacker has TLS network access and low-privileged credentials. Internet exposure, broad internal reachability, excessive account access, and connections to other identity systems increase business risk. The sources do not identify specific connector types, configurations, ports, or deployment patterns.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not identified as CISA KEV-listed in the bundle. However, Oracle describes the issue as easily exploitable by a low-privileged network attacker. Treat reachable affected deployments as urgent without claiming confirmed exploitation.
Researcher notes
The changed-scope vector indicates compromise can affect resources beyond the vulnerable connector. Public details in the bundle do not identify the flawed authorization path, affected connector integrations, indicators of compromise, patch identifiers, or confirmed exploit availability. Testing should remain defensive and authorized; consult Oracle's advisory for implementation-specific remediation details.
Mitigation direction
- Follow Oracle's advisory for the vendor-approved remediation applicable to each affected version.
- Restrict TLS access to trusted management networks and explicitly required systems.
- Review and reduce low-privileged accounts that can access the connector.
- Segment affected connectors from unrelated systems until remediation is verified.
- Monitor Oracle guidance for updated remediation or detection information.
Validation and detection
- Inventory Oracle Identity Manager Connector instances and confirm their exact versions.
- Identify which users and systems can reach each connector over TLS.
- Verify vendor remediation is installed according to Oracle's advisory.
- Review authentication, authorization, and administrative logs for unexplained access or configuration changes.
- Assess connected products for impact if connector compromise is suspected.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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.
Open ATT&CK lookupCVE-2026-60990 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16oracleVulnerability scoring details
Base CVSS 3.1 score
9.9CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Oracle AdvisoryCVE reference, oracle · vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.