dbcve.org
Application Performance ManagementApplication · Oracle

CVE-2026-46858

CRITICAL · 9.1 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 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 APM - Application Performance Management product of Oracle Enterprise Manager (component: JADM, JVM Diagnostics). Supported versions that are affected are 13.5 and 24.1. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise APM - Application Performance Management. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all APM - Application Performance Management accessible data and unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of APM - Application Performance Management. CVSS 3.1 Base Score 9.1 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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

Unauthenticated HTTP network attackers can exploit a vulnerability in Oracle Enterprise Manager's APM (Application Performance Management) JADM/JVM Diagnostics component. Successful exploitation grants attackers unauthorized creation, deletion, or modification of critical data, plus the ability to cause complete denial of service through system crashes or hangs. The CVSS vector indicates no confidentiality impact but high integrity and availability impacts.

MitigationApply Oracle security patches for Enterprise Manager APM versions 13.5 and 24.1 as soon as Oracle releases them. Until then, restrict network access to APM interfaces to trusted networks only and monitor for unauthorized access attempts.

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
Application Performance ManagementApplication
Affected:= 13.5= 24.1

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
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 Oracle APM installation and version
    Locate the Oracle Enterprise Manager installation directory and check the APM component version. Common locations include $ORACLE_HOME/em/ directory or check the Oracle inventory. Look for version files or use 'opatch lsinventory' for Oracle products.
    Affected if The installed Oracle Application Performance Management version is exactly 13.5 or 24.1
  2. Verify JADM/JVM Diagnostics component presence
    Check if the JADM (Java Application Diagnostics Manager) or JVM Diagnostics component is installed and enabled within the APM setup. Review APM configuration files in the diagnostics directory or check the Enterprise Manager console for JADM/JVM Diagnostics module status.
    Affected if The JADM/JVM Diagnostics component is present and enabled in the APM installation
  3. Confirm APM HTTP interface exposure
    Examine network configuration to determine if the APM HTTP interfaces are accessible from network sources. Review web server configuration, load balancer rules, or firewall policies that govern access to the APM console and diagnostic endpoints.
    Affected if APM HTTP interfaces are exposed to untrusted or external network sources rather than restricted to trusted internal networks
  4. Audit JADM/JVM Diagnostics configurations
    Review configuration files associated with JADM/JVM Diagnostics for any unauthorized or unexpected modifications. Check for altered settings in diagnostic configuration files, especially those controlling data creation, modification, or deletion permissions.
    Affected if Unexpected configurations are found or unauthorized changes exist in JADM/JVM Diagnostics settings

A user is affected if they have Oracle Application Performance Management versions 13.5 or 24.1 with the JADM/JVM Diagnostics component enabled and its HTTP interfaces accessible 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle security patches for Enterprise Manager APM versions 13.5 and 24.1 as soon as Oracle releases them. Until then, restrict network access to APM interfaces to trusted networks only and monitor for unauthorized access attempts.

Fix this in Application Performance Management Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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