CVE-2026-60226: Vulnerability in the Oracle Coherence product of Oracle Fusion Middleware (component: Core).
Vulnerability in the Oracle Coherence product of Oracle Fusion Middleware (component: Core). Supported versions that are affected are 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0 and 15.1.1.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via TCP to compromise Oracle Coherence. Successful attacks of this vulnerability can result in takeover of Oracle Coherence. 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
This critical Oracle Coherence vulnerability could let an unauthenticated attacker take control of an affected deployment through reachable TCP services. A successful compromise could expose sensitive data, permit unauthorized changes, and disrupt service. Prioritize systems accessible from untrusted networks, while treating internal-only deployments as still at risk from compromised network footholds.
Executive priority
Treat this as an immediate remediation priority, especially for externally reachable or business-critical Coherence systems. Assign ownership now, establish the affected inventory, reduce network exposure, and follow Oracle guidance. Escalate any evidence of unauthorized access to incident response because successful exploitation may provide complete control of the affected platform.
Technical view
CVE-2026-60226 affects Oracle Coherence Core versions 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, and 15.1.1.0.0. It is classified as CWE-284. The CVSS 3.1 score is 9.8 because exploitation requires network access but no authentication, privileges, user interaction, or high-complexity conditions, with high confidentiality, integrity, and availability impact.
Likely exposure
Exposure exists where an affected Oracle Coherence version accepts TCP connections from an attacker-reachable network. Internet-facing or broadly reachable services carry the greatest urgency. The supplied evidence does not identify ports, configurations, or deployment modes required beyond TCP network access, so organizations must validate their own topology and access controls.
Exploitation context
Oracle describes the vulnerability as easily exploitable and capable of complete Oracle Coherence takeover. However, the supplied record marks KEV false and provides no evidence of active exploitation, public proof-of-concept code, or observed attacks. Absence from KEV does not reduce the underlying technical severity.
Researcher notes
The public bundle establishes network-based, unauthenticated, low-complexity compromise with high impact across all three security properties. It does not disclose the vulnerable code path, affected TCP ports, exploitation prerequisites beyond network access, indicators of compromise, or technical patch details. Testing should remain defensive and authorized; consult Oracle's advisory for product-specific remediation information.
Mitigation direction
Review Oracle's July 2026 advisory for the supported remediation applicable to each affected deployment.
Apply Oracle-provided updates or instructions after appropriate compatibility and recovery testing.
Restrict Coherence TCP access to explicitly authorized systems and trusted network segments.
Remove unnecessary external exposure and monitor affected services until remediation is confirmed.
Validation and detection
Inventory Oracle Coherence deployments and compare exact versions with the four affected releases.
Map which systems and network zones can reach each Coherence TCP service.
Confirm remediation status against Oracle's July 2026 advisory and deployment records.
Reassess TCP reachability after changes to ensure only authorized sources retain access.
Review available telemetry for unexpected connections or unauthorized activity involving affected services.
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-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.
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-284 · source CWE mapping
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.