Skip to content
Web

CVE-2026-60653

8.1
High
EPSS 0.36%Patch availableJul 22, 2026

Authenticated HTTP flaw in Oracle WebCenter Content allows content modification and data access.

common questions

Is CVE-2026-60653 being exploited?

Not confirmed. CVE-2026-60653 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.36% probability of exploitation in the next 30 days.

How severe is CVE-2026-60653?

CVE-2026-60653 is rated High with a CVSS score of 8.1. 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-60653?

Yes. A fix has been recorded for CVE-2026-60653. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-60653 affect?

CVE-2026-60653 affects Oracle WebCenter Content 12.2.1.4.0, Oracle WebCenter Content 14.1.2.0.0, Oracle Fusion Middleware - Web Content Management. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-60653?

Apply vendor patch when released; restrict/segregate WebCenter access, block external HTTP, and monitor logs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Oracle WebCenter Content 12.2.1.4.0Oracle WebCenter Content 14.1.2.0.0Oracle Fusion Middleware - Web Content Management
impact

Low-privileged remote attacker via HTTP can create, delete, or modify content and access sensitive WebCenter data.

action required

Immediate action required

affected versions
Oracle Corporation Oracle WebCenter Content
  • affected12.2.1.4.0
  • affected14.1.2.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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free