dbcve.org
Enterprise Manager Base PlatformApplication · Oracle

CVE-2026-46856

CRITICAL · 9.6 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 →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

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: Metadata Plugin). Supported versions that are affected are 13.5 and 24.1. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Enterprise Manager Base Platform. Successful attacks require human interaction from a person other than the attacker and 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 takeover of Oracle Enterprise Manager Base Platform. CVSS 3.1 Base Score 9.6 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/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 · high confidence

Unauthenticated HTTP vulnerability in the Metadata Plugin component of Oracle Enterprise Manager Base Platform versions 13.5 and 24.1 allows complete system takeover via network access. The attack requires human interaction from a person other than the attacker, and due to scope change, may impact additional products beyond the Enterprise Manager platform.

MitigationApply Oracle security patches when released; as immediate mitigation, restrict network access to Oracle Enterprise Manager HTTP interfaces and implement network segmentation to limit exposure.

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
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/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. Identify if Oracle Enterprise Manager is installed
    Check for Oracle Enterprise Manager installation directories or installed software inventory. Common paths include $ORACLE_HOME/em and /opt/oracle/em. On Windows, check Program Files for Oracle Enterprise Manager.
    Affected if Oracle Enterprise Manager Base Platform is found on the system
  2. Determine the installed version of Oracle Enterprise Manager
    Locate the version file or use Enterprise Manager command-line tools. The version should match 13.5.0.0 or 24.1.0.0.0 specifically. Check $ORACLE_HOME/em/ disks/version or use 'emctl status' command if available.
    Affected if Installed version is exactly 13.5.0.0 or 24.1.0.0.0
  3. Check if Metadata Plugin component is present and enabled
    Review Enterprise Manager plugin configuration files and deployment status. The Metadata Plugin must be present and configured for the vulnerability to be exploitable. Check plugin deployment status via EM console or command line.
    Affected if Metadata Plugin is deployed and enabled in the Enterprise Manager configuration
  4. Assess network exposure of Enterprise Manager HTTP interfaces
    Review firewall rules, network configurations, and access controls surrounding the Enterprise Manager HTTP/HTTPS listeners. Determine if the management ports (typically 7800-7803, 4889, or 1159) are accessible from untrusted networks.
    Affected if Enterprise Manager HTTP interfaces are accessible from untrusted or public networks without proper access restrictions

A user is affected if they have Oracle Enterprise Manager Base Platform versions 13.5.0.0 or 24.1.0.0.0 installed with the Metadata Plugin enabled and HTTP interfaces exposed to untrusted networks.

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 security patches when released; as immediate mitigation, restrict network access to Oracle Enterprise Manager HTTP interfaces and implement network segmentation to limit exposure.

Recommended fix Moderate confidence

Oracle Enterprise Manager 13.5.1 or later, or 24.2 or later

  1. 1. Back up the Oracle Enterprise Manager database and configuration files before any upgrade or patch operation.
  2. 2. Download the latest Oracle Enterprise Manager 13.5.x or 24.2.x (or later) installation media from Oracle Technology Network or My Oracle Support.
  3. 3. Review the Oracle Enterprise Manager Upgrade Guide for your target version for prerequisites and migration procedures.
  4. 4. Stop all Oracle Enterprise Manager services (using 'emctl stop all') before beginning the upgrade.
  5. 5. Execute the upgrade following Oracle's documented procedures for your target version.
  6. 6. After upgrade completes, verify all services start successfully using 'emctl status all'.
  7. 7. Apply the latest Critical Patch Update (CPU) after upgrade to ensure all security patches are included.
Caveat Major version upgrades may require database migration and configuration changes; review Oracle's upgrade documentation for compatibility requirements and downtime windows

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

Fix this in Enterprise Manager Base Platform Scoped from the published advisory
  • Consultation5.0 h
  • Implementation10.0 h
  • Testing8.0 h
  • Review / QA3.0 h
26.0 hours of engineering $4,540
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46856 — 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-46856 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