dbcve.org
Enterprise Manager Base PlatformApplication · Oracle

CVE-2026-46872

CRITICAL · 9.0 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vulnerability in the Oracle Enterprise Manager Base Platform product of Oracle Enterprise Manager (component: Install). Supported versions that are affected are 13.5 and 24.1. Easily exploitable vulnerability allows high privileged attacker with network access via HTTPS to compromise Oracle Enterprise Manager Base Platform. While the vulnerability is in Oracle Enterprise Manager Base Platform, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Enterprise Manager Base Platform accessible data as well as unauthorized read access to a subset of Oracle Enterprise Manager Base Platform accessible data and unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle Enterprise Manager Base Platform. CVSS 3.1 Base Score 9.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:H/A:H).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Vulnerability in the Install component of Oracle Enterprise Manager Base Platform (versions 13.5 and 24.1) allows a high-privileged attacker with network access via HTTPS to create, delete, or modify critical data, read a subset of accessible data, or cause complete denial of service. The scope change indicates attacks can impact additional products beyond the initially affected component.

MitigationApply Oracle Critical Patch Update when available; until then, restrict network access to the Install component to high-privileged authenticated users only and monitor for suspicious installation activity.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Enterprise Manager Base PlatformApplication
Affected:= 13.5.0.0= 24.1.0.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Oracle Enterprise Manager Base Platform is installed
    Check for the presence of Oracle Enterprise Manager by examining the Oracle inventory or looking for the installation directory (typically $ORACLE_HOME/em or similar). On Linux/Unix, review /etc/oraInst.loc for the inventory location, or check for /u01/app/oracle/product/em/* directories.
    Affected if Oracle Enterprise Manager Base Platform is not installed on the system.
  2. Determine the installed version of Oracle Enterprise Manager
    Locate the version file in the Oracle Enterprise Manager home directory. Check $ORACLE_HOME/em/EMGC_DomainEMGC.ear/VERSION.txt or examine the Oracle inventory file for the EM Base Platform version entry. Run: cat $ORACLE_HOME/inventory/ContentsXML/oraclehomeproperties.xml or grep for version in the Oracle inventory.
    Affected if The installed version matches exactly 13.5.0.0 or 24.1.0.0.0.
  3. Confirm the Install component is exposed and accessible
    Review the Oracle Enterprise Manager configuration files (emoms.properties, emomsCfg.xml) in $ORACLE_HOME/sysman/config to determine if the Install functionality is enabled and accessible via the EM console. Check for endpoints related to /install or setup operations.
    Affected if The Install component is enabled and exposed through the EM console HTTPS interface.
  4. Assess network accessibility to the Install component
    Verify that the Oracle Enterprise Manager console is accessible over HTTPS from the network. Test connectivity to the console URL (typically https://hostname:7802/em or port 5500). Review web server configuration and firewall rules to confirm the Install endpoint is reachable.
    Affected if The Install component is accessible over the network on HTTPS without additional access controls.

The system is affected only if Oracle Enterprise Manager Base Platform versions 13.5.0.0 or 24.1.0.0.0 are installed AND the Install component is network-accessible via HTTPS.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update when available; until then, restrict network access to the Install component to high-privileged authenticated users only and monitor for suspicious installation activity.

Recommended fix Moderate confidence

Contact Oracle Support for the specific patched version; Oracle Enterprise Manager 13.5 and 24.1 receive patches via Oracle Critical Patch Updates

  1. 1. Subscribe to Oracle Critical Patch Updates (CPU) at https://www.oracle.com/security-alerts/ to receive notifications for future patches to Oracle Enterprise Manager.
  2. 2. Contact Oracle Support directly to request the specific patch for CVE-2026-46872 for your version (13.5.x or 24.1.x).
  3. 3. Before applying any patch, take a complete backup of the Oracle Enterprise Manager database and Oracle Management Service (OMS) home directory.
  4. 4. Stop all Oracle Enterprise Manager services using 'emctl stop oms -all'.
  5. 5. Apply the Oracle-provided patch following the patch readme instructions specific to your platform and version.
  6. 6. Verify the patch was applied successfully using 'opatch lspatches' or as documented in the patch readme.
  7. 7. Start Oracle Enterprise Manager services using 'emctl start oms'.
  8. 8. Verify the installation is functioning correctly and the vulnerability is addressed.
Caveat No breaking changes typically expected from security patches; minor risk of post-patch configuration resets requiring reconfiguration

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Enterprise Manager Base Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46872 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46872 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data