Security readout for executives and security teams
Plain-English summary
A critical Oracle Coherence flaw could let an unauthenticated attacker who can reach the service over TCP take control of it. A successful attack could expose data, alter system state, and disrupt availability. Risk is highest where affected Coherence services are reachable from untrusted networks.
Executive priority
Treat this as an urgent remediation item. Prioritize rapid inventory and containment immediately, then follow Oracle's authoritative remediation guidance. Systems exposed to the internet or supporting sensitive and critical workloads should receive the highest priority because successful compromise could enable full service takeover.
Technical view
CVE-2026-60224 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 and requires network access over TCP, with no authentication or user interaction. Oracle assigns CVSS 3.1 score 9.8 and reports potential complete confidentiality, integrity, and availability impact.
Likely exposure
Exposure exists when an affected Oracle Coherence version is deployed and its TCP service is reachable by a potential attacker. Internet-facing instances are especially concerning, but internal exposure also matters where networks are shared, compromised, or insufficiently segmented. The source bundle does not identify specific ports, configurations, or deployment patterns.
Exploitation context
The vulnerability is described as easily exploitable and capable of Coherence takeover. However, it is not listed as a CISA KEV in the supplied bundle, and no supplied source establishes active exploitation, public exploit availability, or observed attacks. Treat technical severity and exploitation evidence as separate risk signals.
Researcher notes
The supplied evidence establishes an unauthenticated, low-complexity, network-reachable authorization weakness with complete impact metrics. It does not provide root-cause details, affected protocol specifics, patch identifiers, indicators of compromise, or exploit telemetry. Validation should remain defensive and version- and reachability-focused until Oracle publishes or confirms additional technical guidance.
Mitigation direction
- Identify every deployment running an affected Oracle Coherence version.
- Restrict Coherence TCP access to explicitly trusted systems and networks.
- Remove unnecessary public or cross-segment reachability while remediation is assessed.
- Review Oracle's July 2026 advisory for authoritative patching or upgrade instructions.
- Prioritize remediation for externally reachable and business-critical deployments.
Validation and detection
- Confirm deployed Coherence versions against the four affected versions.
- Map which systems and network zones can reach each Coherence TCP service.
- Verify temporary access controls deny traffic from untrusted networks.
- Confirm remediation status using Oracle's advisory and approved change records.
- Monitor Coherence and network logs for unexpected connections or suspicious administrative activity.
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-60224 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.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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:N/UI:N/S:U/C:H/I:H/A:H3.95.9oracleVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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.