dbcve.org
CoherenceApplication · Oracle

CVE-2026-60271

HIGH · 7.8 CVSS v3.1 Developing Published 2026-07-21
No fix yet
No fix has been published. The vendor has not shipped a fixed release or patch. You remain exposed.
See remediation →
80/100
Remediation priority · High
Zero-click 4 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 logon to the infrastructure where Oracle Coherence executes to compromise Oracle Coherence. Successful attacks of this vulnerability can result in takeover of Oracle Coherence. CVSS 3.1 Base Score 7.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-08-04.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CoherenceApplication
Affected:= 12.2.1.4.0= 14.1.1.0.0= 14.1.2.0.0= 15.1.1.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Recommended fix Moderate confidence

Upgrade to the latest Oracle Coherence 14.1.x or 15.1.x release as listed in Oracle's Critical Patch Update

  1. 1. Identify the current Oracle Coherence version in use by checking the installation directory or using the coherence.sh/version script
  2. 2. Navigate to Oracle's official security alerts page at https://www.oracle.com/security-alerts/ to check for available patches for this vulnerability
  3. 3. If a patch is available, download and apply the relevant Critical Patch Update (CPU) for Oracle Coherence
  4. 4. Alternatively, upgrade to a fixed version of Oracle Coherence that addresses the vulnerability - check Oracle's lifetime support policy for the latest supported releases
  5. 5. After applying the patch or upgrade, restart the Oracle Coherence services in a controlled manner
  6. 6. Verify the fix by confirming the Coherence version matches the patched release and run basic functionality tests
  7. 7. Review Oracle's advisory for any additional configuration changes or workarounds required
Caveat Oracle major version upgrades may require compatibility testing; review Oracle's upgrade documentation for migration considerations

Generated from the published advisory — verify against the referenced sources before acting.

No vendor fix exists Coherence has not published a patch for this.

There is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.

Add your voice

Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.

Can’t wait

We develop and verify an original fix where the vendor hasn’t, from $1,950. Deployed to your staging first — never straight to production.

Scope it with us

See what else the community needs solved on the solutions-needed board.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-60271 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-60271 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data