PatchSiren cyber security CVE debrief
CVE-2026-60282 Oracle CVE debrief
The CVE-2026-60282 vulnerability is a medium-severity issue affecting Oracle Coherence, a product of Oracle Fusion Middleware. The vulnerability is located in the Core component and has a CVSS score of 5.4. It allows a low-privileged attacker with network access via TCP to compromise Oracle Coherence, potentially leading to unauthorized data access and modification. Organizations should review their deployments and apply patches or mitigations as necessary.
- Vendor
- Oracle
- Product
- Coherence
- CVSS
- MEDIUM 5.4
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-21
- Original CVE updated
- 2026-08-07
- Advisory published
- 2026-07-21
- Advisory updated
- 2026-08-07
Who should care
Organizations using Oracle Coherence versions 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, and 15.1.1.0.0 should prioritize patching this vulnerability to prevent potential data breaches and unauthorized access. Security teams, vulnerability management teams, and operators of affected systems should review and act on this vulnerability.
Technical summary
The CVE-2026-60282 vulnerability is a medium-severity issue affecting Oracle Coherence, a product of Oracle Fusion Middleware. The vulnerability is located in the Core component and has a CVSS score of 5.4. It allows a low-privileged attacker with network access via TCP to compromise Oracle Coherence, potentially leading to unauthorized data access and modification. Organizations should review their deployments and apply patches or mitigations as necessary to prevent potential data breaches and unauthorized access. Security teams, vulnerability management teams, and operators of affected systems should review and act on this vulnerability. The affected product deployments exist in managed environments and should be verified by defenders. The official advisory or CVE record should be reviewed to validate affected scope, severity, and vendor guidance.
Defensive priority
Medium priority given the CVSS score of 5.4 and the potential for unauthorized update, insert or delete access to some Oracle Coherence accessible data as well as unauthorized read access to a subset of Oracle Coherence accessible data.
Recommended defensive actions
- Inventory and verify affected Oracle Coherence versions
- Apply vendor patches or updates
- Implement compensating controls to restrict network access
- Monitor for suspicious activity
- Review and update security configurations
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
Evidence notes
The CVE-2026-60282 vulnerability affects Oracle Coherence versions 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, and 15.1.1.0.0. It allows a low-privileged attacker with network access via TCP to compromise Oracle Coherence, potentially leading to unauthorized data access and modification. Defenders should verify affected product deployments and review official advisories for mitigation guidance.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-60282 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-60282
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-60282 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-60282
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Mitigation or vendor reference
Unverified legacy reference
URL: https://www.oracle.com/security-alerts/cpujul2026.html
[email protected] - Vendor Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.