CVE-2026-46998
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 · uneditedVulnerability 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 HTTPS to compromise Oracle Enterprise Manager Base Platform. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of Oracle Enterprise Manager Base Platform. CVSS 3.1 Base Score 8.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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 confidenceThis is an unauthenticated remote code execution vulnerability in Oracle Enterprise Manager Base Platform's Metadata Plugin component. Attackers can exploit this via HTTPS with only human interaction required (like clicking a malicious link), potentially achieving complete system compromise including full confidentiality, integrity, and availability impacts.
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= 13.5.0.0= 24.1.0.0.0CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Oracle Enterprise Manager Base Platform is installedLocate the Oracle Enterprise Manager installation directory (typically $ORACLE_HOME/em or check running processes for 'emctl' or 'oracle.em.*' services)Affected if The software is not present, then not affected
-
Determine the installed version of Oracle Enterprise Manager Base PlatformRun 'emctl status agent' or check the Oracle inventory via 'opatch lsinventory' for the Enterprise Manager Base Platform component, or access the Enterprise Manager console and navigate to 'Setup > Manage Cloud > About' to view the versionAffected if Version equals 13.5.0.0 or 24.1.0.0.0 exactly, then affected
-
Verify the Metadata Plugin component is configuredAccess Enterprise Manager console, navigate to 'Setup > Extensions > Plugin' or check the plugin deployment status via 'emcli list_plugins' command-line toolAffected if The Metadata Plugin is deployed and active, then potentially affected
-
Check if HTTPS listener is exposed on network interfacesReview the Oracle Enterprise Manager listener configuration (typically in 'listener.ora' or via 'lsnrctl status') and verify which network interfaces the OMS (Oracle Management Service) is bound toAffected if The EM console is accessible via HTTPS from untrusted networks, then exposed and potentially affected
-
Review access logs for suspicious requests to Metadata Plugin endpointsExamine EM security logs (located in $ORACLE_HOME/em/EMGC_OracleDB/sysman/log/) for unusual POST requests to Metadata Plugin URLs or unexpected authentication attemptsAffected if Anomalous requests targeting Metadata Plugin are found, then may indicate exploitation attempts
You are affected if Oracle Enterprise Manager Base Platform versions 13.5.0.0 or 24.1.0.0.0 are installed with the Metadata Plugin enabled and the HTTPS interface is network-accessible.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply the latest Oracle Critical Patch Update (CPU) for Oracle Enterprise Manager that addresses this vulnerability. Since the vulnerability requires human interaction, also implement network segmentation and restrict external access to the Enterprise Manager console.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46998 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-46998 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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