Security readout for executives and security teams
Plain-English summary
This critical Oracle Coherence flaw could let an unauthenticated network attacker take over an affected deployment. A successful compromise could expose data, permit unauthorized changes, and disrupt services that depend on the Coherence cluster. Risk is greatest where Coherence TCP services are reachable from untrusted networks.
Executive priority
Treat this as an urgent remediation item. Identify exposed affected versions immediately, restrict network access, and follow Oracle's vendor guidance. Give highest priority to internet-reachable clusters and systems supporting sensitive data or critical services because successful exploitation could produce complete confidentiality, integrity, and availability loss.
Technical view
CVE-2026-60288 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. The vulnerability requires TCP network access but no credentials or user interaction. Its CVSS 3.1 score is 9.8, with high confidentiality, integrity, and availability impact. The record associates it with CWE-306, missing authentication for a critical function.
Likely exposure
Potentially exposed systems are Oracle Coherence deployments running an explicitly affected version with attacker-accessible TCP connectivity. Internet-facing access creates the clearest concern, but internal exposure also matters because compromised hosts or unauthorized users may provide the required network path. The bundle does not identify specific ports or configurations.
Exploitation context
The vulnerability is described as easily exploitable and capable of complete Coherence takeover. However, the supplied bundle marks it as absent from KEV and provides no evidence of active exploitation or a public exploit. Treat exploit status as unconfirmed, not as evidence that exploitation is impossible.
Researcher notes
The available evidence establishes remote, unauthenticated TCP exploitation and potential product takeover, but does not describe the vulnerable protocol path, affected ports, attack mechanics, patch identifiers, indicators of compromise, or observed campaigns. Avoid assuming all Coherence releases are affected; scope is limited to the four listed versions.
Mitigation direction
- Check Oracle's July 2026 advisory for the vendor-approved update or remediation applicable to each affected release.
- Prioritize affected deployments reachable from the internet or other untrusted network segments.
- Restrict Coherence TCP access to explicitly authorized systems while remediation is pending.
- Isolate affected clusters supporting sensitive or business-critical workloads until exposure is reduced.
Validation and detection
- Inventory Oracle Coherence deployments and confirm their exact installed versions.
- Map TCP reachability to each affected cluster from internet, user, partner, and server networks.
- Confirm vendor-recommended remediation is installed using authoritative version or patch records.
- Review network and application telemetry for unexpected Coherence connections, configuration changes, or administrative activity.
- Retest network restrictions after remediation to confirm only authorized systems retain access.
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-306: 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.
Open ATT&CK lookupCVE-2026-60288 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.
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.