Treat this CVSS 8.6 with caution. The score derives entirely from High Confidentiality impact while explicitly encoding zero Integrity and zero Availability compromise — a structural anomaly for WebLogic Core vulnerabilities, which historically manifest as full remote code execution through T3/IIOP deserialization. This compressed vector suggests Oracle has identified a narrow exploitation path, likely a specific deserialization gadget chain or constrained MBean interface that permits data exfiltration but doesn't directly chain to code execution. Do not interpret this as a low-severity flaw. The scope change notation indicates Oracle acknowledges the impact extends beyond WebLogic itself to adjacent Oracle products — databases, identity stores, or Fusion Middleware components that WebLogic connects to. A confidentiality-only flaw in this context may serve as the reconnaissance stage of a broader attack chain rather than the terminal payload. The EPSS of 0.4% is unreliable for prioritization: Oracle T3/IIOP vulnerabilities with modest EPSS scores have historically climbed rapidly once public PoCs emerge, often within the same Critical Patch Update cycle. More critically, this flaw lacks the host-level detection signals that RCEs trigger — no anomalous process spawning, no network-level behavioral alerts. Exfiltration occurs silently, and dwell time may be unbounded until logs are reviewed or data surfaces externally. Patch it, but also extend logging and monitoring beyond your WebLogic tier to cover backend data stores and identity infrastructure — assume the blast radius exceeds what the CVSS vector describes.
CVE-2026-60699
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 · uneditedVulnerability in the Oracle WebLogic Server 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 T3, IIOP to compromise Oracle WebLogic Server. While the vulnerability is in Oracle WebLogic Server, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle WebLogic Server accessible data. CVSS 3.1 Base Score 8.6 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N).
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 analysisThe application fails to correctly restrict what a user can do or reach, so functions or resources are available to people who should not have them. Attackers simply probe for the paths where the check is missing or wrong. The fix is to enforce access-control decisions consistently on every request, evaluated against the acting user rather than assumed from context.
General guidance for the improper access control class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
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.
From vendor dataThere 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.
Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.
We develop and verify an original fix where the vendor hasn’t, from $4,900. Deployed to your staging first — never straight to production.
Scope it with usSee what else the community needs solved on the solutions-needed board.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-60699 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesTreat this CVSS 8.6 with caution. The score derives entirely from High Confidentiality impact while explicitly encoding zero Integrity and zero Availability compromise — a structural anomaly for WebLogic Core vulnerabilities, which historically manifest as full remote code execution through T3/IIOP deserialization. This compressed vector suggests Oracle has identified a narrow exploitation path, likely a specific deserialization gadget chain or constrained MBean interface that permits data exfiltration but doesn't directly chain to code execution. Do not interpret this as a low-severity flaw. The scope change notation indicates Oracle acknowledges the impact extends beyond WebLogic itself to adjacent Oracle products — databases, identity stores, or Fusion Middleware components that WebLogic connects to. A confidentiality-only flaw in this context may serve as the reconnaissance stage of a broader attack chain rather than the terminal payload. The EPSS of 0.4% is unreliable for prioritization: Oracle T3/IIOP vulnerabilities with modest EPSS scores have historically climbed rapidly once public PoCs emerge, often within the same Critical Patch Update cycle. More critically, this flaw lacks the host-level detection signals that RCEs trigger — no anomalous process spawning, no network-level behavioral alerts. Exfiltration occurs silently, and dwell time may be unbounded until logs are reviewed or data surfaces externally. Patch it, but also extend logging and monitoring beyond your WebLogic tier to cover backend data stores and identity infrastructure — assume the blast radius exceeds what the CVSS vector describes.
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-60699 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
- 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