CVE-2026-60253: 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
An unauthenticated attacker who can reach a vulnerable Oracle Coherence service over TCP may take complete control of it. A successful compromise could expose data, alter application state, and disrupt services relying on the Coherence deployment.
Executive priority
Treat this as an immediate remediation priority for exposed or business-critical Coherence systems. Assign owners now, restrict unnecessary network reachability, and apply Oracle guidance after expedited testing. Investigate potentially exposed systems because patching alone does not determine whether earlier compromise occurred.
Technical view
CVE-2026-60253 is a CWE-306 authentication weakness in Oracle Coherence Core. It affects versions 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, and 15.1.1.0.0. Exploitation requires TCP network access but no privileges or user interaction. CVSS 3.1 is 9.8, with high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is highest where an affected Coherence service is reachable from untrusted networks or broadly accessible internal segments. The supplied evidence does not identify specific ports, configurations, deployment patterns, or compensating controls required for exploitation.
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, public exploit code, or observed attacks. Absence from KEV does not prove exploitation is not occurring.
Researcher notes
The source identifies network reachability, low attack complexity, absent authentication, and full CIA impact, but does not describe the vulnerable code path, required service configuration, affected port, indicators of compromise, or patch identifiers. Validation should therefore combine version evidence, network-path review, Oracle guidance, and retrospective telemetry.
Mitigation direction
Inventory Oracle Coherence deployments and identify the installed version.
Prioritize systems reachable from the internet, partner networks, or broad internal segments.
Review Oracle's July 2026 advisory and apply its vendor-provided update or remediation.
Restrict TCP access to trusted application hosts until remediation is verified.
Monitor Coherence hosts and network traffic for unexplained access or administrative changes.
Validation and detection
Confirm each deployment is not running a listed affected version.
Verify network controls prevent untrusted TCP access to Coherence services.
Confirm Oracle's recommended update is installed using approved inventory evidence.
Test required application connectivity after restricting access or applying updates.
Review logs and telemetry for suspicious pre-remediation access or configuration changes.
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-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.
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-306 · source CWE mapping
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.