Skip to content
major vulnerability· requires attention

Affects widely used Oracle Enterprise Manager Base Platform; high-severity takeover risk.

Infrastructure

CVE-2026-46875

9.1
Critical
EPSS 0.46%Patch availableJun 17, 2026

Takeover of Oracle Enterprise Manager Base Platform via HTTPS.

common questions

Is CVE-2026-46875 being exploited?

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

How severe is CVE-2026-46875?

CVE-2026-46875 is rated Critical with a CVSS score of 9.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-46875?

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

What does CVE-2026-46875 affect?

CVE-2026-46875 affects Oracle Enterprise Manager Base Platform (Deployment Library) 13.5, 24.1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-46875?

Patch ASAP when released; restrict HTTPS access to OEM Base Platform.

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

executive summary
technical analysis
affected
Oracle Enterprise Manager Base Platform (Deployment Library) 13.5, 24.1
impact

Remote takeover via HTTPS with high privileges; full compromise of OEM Base Platform (C/I/A).

action required

Immediate action required

affected versions
Oracle Corporation Oracle Enterprise Manager Base Platform
  • affected13.5
  • affected24.1

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