CVE-2026-60239: 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 low privileged attacker with network access via HTTP to compromise Oracle Coherence. While the vulnerability is in Oracle Coherence, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Coherence accessible data as well as unauthorized access to critical data or complete access to all Oracle Coherence accessible data. CVSS 3.1 Base Score 9.6 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N).
Security readout for executives and security teams
Plain-English summary
CVE-2026-60239 is a critical access-control vulnerability in Oracle Coherence. A low-privileged attacker who can reach the service over HTTP could read, create, modify, or delete critical accessible data. Effects may extend into connected products, although availability impact is not identified.
Executive priority
Treat as an urgent remediation item because compromise could expose or alter all data accessible through Coherence and affect connected products. Prioritize internet-facing and broadly reachable deployments first. The supplied sources do not confirm active exploitation, so urgency is driven by impact and exploitability rather than observed attacks.
Technical view
Affected Oracle Coherence versions are 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, and 15.1.1.0.0. The flaw is classified as CWE-284 and scores CVSS 9.6: network-accessible, low complexity, low privileges, no user interaction, changed scope, and high confidentiality and integrity impact.
Likely exposure
Exposure is most likely where an affected Coherence version accepts HTTP connections from untrusted or broadly accessible networks and low-privileged accounts exist. The supplied evidence does not identify specific HTTP endpoints, configurations, or dependent products that make exploitation possible.
Exploitation context
The vulnerability is described as easily exploitable by a low-privileged attacker with HTTP network access and requires no user interaction. It is not listed as KEV in the supplied bundle, and no cited evidence establishes active exploitation or public exploit availability.
Researcher notes
The record indicates improper authorization, HTTP reachability, low required privileges, no user interaction, and changed scope. It does not disclose the vulnerable endpoint, authorization failure mechanism, affected dependent products, indicators of compromise, or a specific fixed version. Validate defensively without attempting exploitation in production.
Mitigation direction
Identify every deployment running one of the four affected Oracle Coherence versions.
Restrict HTTP access to trusted networks and authorized administrative paths while remediation is assessed.
Review and minimize low-privileged accounts that can reach Coherence over HTTP.
Consult Oracle's July 2026 advisory for authoritative patching or upgrade instructions.
Prioritize connected environments where Coherence can access critical or shared application data.
Validation and detection
Verify deployed Coherence versions against Oracle's affected-version list.
Map all HTTP ingress paths, including proxies, gateways, management interfaces, and internal network routes.
Confirm low-privileged identities cannot exceed their intended Coherence data permissions.
Review logs for unexpected reads, creations, modifications, deletions, or low-privileged HTTP activity.
After remediation, confirm the installed build matches Oracle guidance and repeat access-control testing.
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: noTechnical 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.