Oracle WebLogic is widely deployed enterprise middleware; unauthenticated remote compromise can expose critical data across organizations.
CVE-2026-60699
Unauthenticated remote compromise of Oracle WebLogic via T3/IIOP
Is CVE-2026-60699 being exploited?
Not confirmed. CVE-2026-60699 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.41% probability of exploitation in the next 30 days.
How severe is CVE-2026-60699?
CVE-2026-60699 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-60699?
Yes. A fix has been recorded for CVE-2026-60699. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-60699 affect?
CVE-2026-60699 affects Oracle WebLogic Server 12.2.1.4.0, Oracle WebLogic Server 14.1.1.0.0, Oracle WebLogic Server 14.1.2.0.0, Oracle WebLogic Server 15.1.1.0.0. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-60699?
Isolate affected servers; block T3/IIOP at network edge; apply vendor patch when available.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker over T3/IIOP can fully compromise WebLogic server and exfiltrate sensitive data (confidentiality loss).
Immediate action required
- affected12.2.1.4.0
- affected14.1.1.0.0
- affected14.1.2.0.0
- affected15.1.1.0.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.