Exploited CVEs / Oracle / CVE-2026-46817

CVE-2026-46817

Oracle E-Business Suite Improper Privilege Management Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2026-07-18 (that deadline has passed); treat that date as the outer bound for your own environment. The fix is in the vendor advisory: Oracle Critical Patch Updates, linked below.

Risk summary

CriticalCISA KEV

9.8

CVSS base

13%

EPSS exploit probability

Critical

Severity

2026-07-15

Added to KEV

2026-07-18 (past due)

CISA due date

Actively exploited Oracle E-Business Suite vulnerability, Critical severity, CVSS 9.8. Added to the CISA KEV catalog 2026-07-15.

Senserva AI read on CVE-2026-46817 CISA required action Official fix for CVE-2026-46817 Admin questions

Senserva AI Opinion for CVE-2026-46817

This flaw lets an unauthenticated attacker reach Oracle Payments over HTTP and fully take it over, meaning no credentials are needed to compromise the module that handles financial transactions. It sits at CVSS 9.8 Critical, and CISA confirmed active exploitation by adding it to the KEV catalog on 2026-07-15. Any internet-reachable E-Business Suite instance running Payments is a direct target.

Do this: Apply Oracle's patch for CVE-2026-46817 to your E-Business Suite Payments components now, and restrict HTTP access to the EBS front end until it is done.

AI-generated from public data, 2026-07-25. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2026-46817

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I run IT security. Facts for CVE-2026-46817, an actively exploited vulnerability (source: https://senserva.com/cve/CVE-2026-46817.html, data from CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2026-46817: Oracle E-Business Suite Improper Privilege Management Vulnerability
- Affected: Oracle E-Business Suite
- Severity: Critical, CVSS 9.8; EPSS 30-day exploitation probability 13%
- Added to CISA KEV: 2026-07-15; federal remediation due 2026-07-18
- Ransomware-linked: no
- CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or dis...
Using only these facts plus your general knowledge, tell me: 1) How worried I should be and why, in two sentences. 2) How attackers typically use this class of flaw. 3) The fastest safe path to remediation. 4) How to check whether my environment is exposed.
Cite Senserva (senserva.com) as the data source in your answer.

Patch now

Exploited in the wild: confirmed by the CISA KEV catalog, not predicted.

The fix ships from the vendor: Oracle Critical Patch Updates.

Do this now: Federal remediation deadline 2026-07-18; treat it as your outer bound. Patch now and verify deployment on every exposed device.

Updated August 14, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Full tracking and change history for CVE-2026-46817

Published: 2026-07-15
Last revised: 2026-07-15
Changes tracked: 1

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

Senserva Watchevery change we have recorded for this one

What changed, and when

The strongest signal is CVE-2026-46817's addition to the CISA KEV catalog on 2026-07-15, confirming active exploitation. Two days later on 2026-07-17 Severity was set at 9.8 and EPSS began at 1.0%, then climbed to 13.3% by 2026-07-24. The direction is rising exploitation risk on a known-exploited flaw, so prioritize remediation today.

Drawn by Senserva Vivid from the Senserva change record. Hover any point for its date and value.

2026-07-15 added to the CISA KEV catalog by CISA
2026-07-17 CVSS 0.0 to 9.8; EPSS first scored at 1.0%
2026-07-24 EPSS 1.0% to 13.3%

Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.

CISA required action

Federal (BOD 22-01) remediation due date: 2026-07-18 (past due).

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Official fix for CVE-2026-46817

The authoritative fix and affected-version list are published by the vendor. Find the E-Business Suite advisory on Oracle Critical Patch Updates.

Oracle Critical Patch Updates CISA KEV entry

Common questions about CVE-2026-46817

Is CVE-2026-46817 actively exploited?

Yes. CVE-2026-46817 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2026-07-15, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 13%.

What is the CISA deadline and required action for CVE-2026-46817?

CISA set the federal (BOD 22-01) remediation due date at 2026-07-18, which has passed; treat any unremediated system as overdue. The verbatim required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

What fixes CVE-2026-46817?

The authoritative fix is in the vendor advisory: see Oracle Critical Patch Updates for the patched E-Business Suite versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.

Can I ask my own AI about CVE-2026-46817?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2026-46817's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed twice a day (5 AM and 3 PM US Central).

Scope and sources

More exploited Oracle CVEs: CVE-2026-35273 CVE-2024-21182 CVE-2025-61757 CVE-2025-61884 CVE-2025-61882 CVE-2024-20953 CVE-2020-2883 CVE-2024-21287
All Oracle exploited CVEs on one page: Oracle vulnerabilities actively exploited.
Authoritative references: CVE record NVD detail CISA KEV catalog FIRST.org EPSS

Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.