Skip to content
major vulnerability· requires attention

Oracle Database is widely used enterprise software; this vulnerability allows full RDBMS takeover and can disrupt organizations globally.

Applications

CVE-2026-61211

CRITICAL
Critical
EPSS 0.44%Patch availableJul 22, 2026

Remote takeover of Oracle Database via DBMS_CLOUD privilege over Oracle Net.

common questions

Is CVE-2026-61211 being exploited?

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

How severe is CVE-2026-61211?

CVE-2026-61211 is rated Critical. 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-61211?

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

What does CVE-2026-61211 affect?

CVE-2026-61211 affects Oracle Database Server RDBMS 19.3 - 19.31, Oracle Database Server RDBMS 23.4.0 - 23.26.2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-61211?

Apply vendor patch when released; revoke/limit Execute DBMS_CLOUD; restrict Oracle Net access.

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

executive summary
technical analysis
affected
Oracle Database Server RDBMS 19.3 - 19.31Oracle Database Server RDBMS 23.4.0 - 23.26.2
impact

Remote full RDBMS takeover by a low-privileged user with Execute DBMS_CLOUD via Oracle Net; high C/I/A and possible lateral compromise.

action required

Immediate action required

affected versions
Oracle Corporation Oracle Database Server
  • affected>= 19.3 and <= 19.31
  • affected>= 23.4.0 and <= 23.26.2

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