Security readout for executives and security teams
Plain-English summary
An unauthenticated attacker who can reach an affected Oracle Coherence service over HTTP may take control of it. A successful compromise could expose data, alter systems, and disrupt availability. The vulnerability is critical because exploitation requires no credentials or user interaction.
Executive priority
Treat as an immediate remediation priority for exposed systems and an urgent priority elsewhere. Assign owners to identify affected Coherence deployments, reduce HTTP reachability, consult Oracle's update guidance, and confirm remediation. Escalate any evidence of unauthorized access or unexplained changes to incident response.
Technical view
CVE-2026-60272 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-306, indicating missing authentication for a critical function. Oracle assigns CVSS 3.1 score 9.8: network-accessible, low complexity, no privileges, no interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is highest where an affected Coherence HTTP interface is reachable from the internet or untrusted networks. Internally reachable deployments also remain at risk from compromised hosts or malicious insiders. The bundle provides no CPEs or deployment-specific indicators, so organizations must inventory versions and verify actual HTTP reachability.
Exploitation context
Oracle describes the flaw as easily exploitable and capable of Coherence takeover. However, the supplied bundle marks it absent from KEV and provides no evidence of active exploitation, public proof-of-concept code, or observed attacks. Exploit availability and current threat activity therefore remain unconfirmed.
Researcher notes
The supplied evidence establishes affected versions, HTTP network access, unauthenticated exploitation, CWE-306, and complete takeover impact. It does not describe the vulnerable endpoint, root cause, patch identifiers, detection signatures, or exploitation telemetry. Validation should remain version-, configuration-, reachability-, and log-focused without attempting exploitation.
Mitigation direction
- Consult Oracle's July 2026 advisory for the applicable security update and installation guidance.
- Prioritize affected instances whose HTTP interfaces are internet-facing or reachable from untrusted networks.
- Restrict HTTP access to explicitly authorized systems until vendor remediation is confirmed.
- Monitor affected services for unexpected access, configuration changes, data access, or disruption.
Validation and detection
- Inventory Oracle Coherence deployments and compare installed versions with the four affected releases.
- Map each affected service's HTTP exposure across internet, partner, user, and internal network paths.
- Confirm Oracle-recommended updates are installed using approved version and patch records.
- Review authentication and access controls protecting Coherence HTTP interfaces.
- Inspect relevant logs and monitoring data for suspicious unauthenticated access or unexplained administrative changes.
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-60272 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.