CVE-2026-46881
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 JD Edwards EnterpriseOne Tools product of Oracle JD Edwards (component: Enterprise Infrastructure Security). Supported versions that are affected are 9.2.0.0-9.2.26.2. Easily exploitable vulnerability allows unauthenticated attacker with network access via JDENET to compromise JD Edwards EnterpriseOne Tools. Successful attacks of this vulnerability can result in takeover of JD Edwards EnterpriseOne Tools. CVSS 3.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 confidenceCritical unauthenticated remote code execution vulnerability in Oracle JD Edwards EnterpriseOne Tools (Enterprise Infrastructure Security component). Attackers can exploit this via JDENET network protocol with no authentication required, achieving complete system compromise across confidentiality, integrity, and availability. Affects versions 9.2.0.0 through 9.2.26.2.
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>= 9.2.0.0, <= 9.2.26.2CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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.
-
Verify JD Edwards EnterpriseOne Tools installationCheck for JD Edwards EnterpriseOne Tools installation directories or services on the system. Common installation paths include C:\Oracle\JD Edwards\EnterpriseOneTools or /opt/oracle/jde/EnterpriseOneTools. Also check Windows Services or Unix process listings for EnterpriseOne-related services.Affected if JD Edwards EnterpriseOne Tools is installed on the system
-
Determine installed version of EnterpriseOne ToolsLocate the version information for the installation. This is typically found in version files within the installation directory, the JD Edwards EnterpriseOne Administrator console, or by querying the installation through the Oracle management interfaces. Compare the version number against the affected range 9.2.0.0 through 9.2.26.2.Affected if Installed version falls within 9.2.0.0 to 9.2.26.2 inclusive
-
Confirm JDENET protocol is enabledVerify that the JDENET network service is enabled and running. JDENET is the network communication protocol for JD Edwards EnterpriseOne. Check for JDENET-related processes, services, or configuration settings that indicate the network listener is active.Affected if JDENET protocol listener is running and accepting connections
-
Assess network exposure of JDENET portsDetermine if the system is directly accessible from untrusted networks. Identify which network interfaces and ports JDENET is bound to. Check firewall rules and network configuration to determine if JDENET ports are exposed to the internet or untrusted internal networks.Affected if JDENET ports are accessible from untrusted network segments or the internet
A system is affected if it runs JD Edwards EnterpriseOne Tools version 9.2.0.0 through 9.2.26.2 with JDENET network protocol exposed to untrusted networks.
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 Oracle's latest Critical Patch Update (CPU) for JD Edwards EnterpriseOne Tools immediately. Until patch is available, restrict network access to JDENET ports and implement additional network segmentation.
- Consultation8.0 h
- Implementation16.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46881 — 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-46881 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