Oracle Database is widely deployed; an unauthenticated network flaw allowing DB crashes and data modification can disrupt enterprise operations and is headline-worthy.
CVE-2026-47046
Unauthenticated network flaw in Oracle RDBMS allows DoS and limited data modification.
Is CVE-2026-47046 being exploited?
Not confirmed. CVE-2026-47046 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-47046?
CVE-2026-47046 is rated High with a CVSS score of 8.2. 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-47046?
Yes. A fix has been recorded for CVE-2026-47046. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-47046 affect?
CVE-2026-47046 affects Oracle Database Server RDBMS 23.4.0 - 23.26.2, Oracle Net (listener/network interface). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-47046?
Apply Oracle patch ASAP; block Oracle Net from untrusted networks; verify backups and monitor DB activity.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote unauthenticated attacker via Oracle Net can hang/crash the DB (DoS) and perform UPDATE/INSERT/DELETE on some accessible data.
Immediate action required
- 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.