CVE-2026-60309 Oracle CVE debrief

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. The vulnerability's high CVSS score of 8.8 indicates a significant risk, with impacts on confidentiality, integrity, and availability. Affected operators, platforms, vulnerability-management, and security teams should review and act on this vulnerability.

Technical summary

The vulnerability in Oracle Coherence has a CVSS 3.1 Base Score of 8.8, indicating high impacts on confidentiality, integrity, and availability. The CVSS vector is CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, showing that the vulnerability can be exploited by an unauthenticated attacker with access to the physical communication segment (AV:A), with low attack complexity (AC:L), and without requiring user interaction (UI:N).

Defensive priority

Highest based on CVSS score and potential impact on confidentiality, integrity, and availability for affected product deployments in managed environments and assign an owner for follow-up. Review compensating controls for exposed systems while remediation is scheduled and verified. Track exceptions, retest remediated assets, and close the item only after evidence is documented. Monitor for any suspicious activity around Oracle Coherence instances. Perform regular inventory checks to ensure all instances of Oracle Coherence are accounted for and patched. Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up. Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed. Check relevant monitoring, detection, and logs for exposed assets that need extra review. Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. Defenders should verify affected product deployments and review official advisories. Evidence is limited to CVE.org and NVD data. Defenders should verify affected product deployments and review official advisories. Evidence is limited to CVE.org and NVD data. Defenders should verify affected product deployments and review official advisories. Evidence is limited to CVE.org and NVD data. Defenders should verify affected product deployments and review official advisories. Evidence is limited to CVE.org and NVD data. Defenders should verify affected product deployments and review official advisories. Evidence is limited to CVE.org and NVD data. Defenders should verify affected product deployments and review official advisories. Evidence is limited to CVE.org and NVD data. Defenders should verify affected product deployments and review official advisories. Evidence is limited to CVE.org and NVD data. Defenders should verify affected product deployments and review official advisories. Evidence is limited to CVE.org and NVD data. Defenders should verify affected product deployments and review official advisories. Evidence is limited to CVE.org and NVD data. Defenders should verify affected product deployments, 7

Recommended defensive actions

• Apply the patches provided by Oracle as soon as possible.
• Implement compensating controls such as network segmentation to limit access to the affected systems.
• Monitor for any suspicious activity around Oracle Coherence instances.
• Perform regular inventory checks to ensure all instances of Oracle Coherence are accounted for and patched.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Evidence notes

The CVE record was published on 2026-07-21T22:17:33.603Z and was last modified on 2026-07-27T20:19:50.853Z. The NVD entry is currently Analyzed. The vulnerability details are based on the information provided by the CVE.org and NVD. Evidence is limited to CVE.org and NVD data. Defenders should verify affected product deployments and review official advisories.

Sources and references

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.