CVE-2026-46882
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 confidenceA critical unauthenticated remote code execution vulnerability in the Enterprise Infrastructure Security component of JD Edwards EnterpriseOne Tools (versions 9.2.0.0-9.2.26.2). The flaw is exploitable via the JDENET network protocol, allowing an unauthenticated attacker to achieve complete system compromise (full confidentiality, integrity, and availability impact).
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.
-
Identify JD Edwards EnterpriseOne Tools installationCheck for EnterpriseOne Tools installation by looking for the installation directory, typically under $JDE_HOME or %JDE_HOME%, or search for JDE processes in running task listAffected if JD Edwards EnterpriseOne Tools software is present on the system
-
Determine installed EnterpriseOne Tools versionLocate the version file or check the installed package version. Common locations include the installation directory or registry entries. Run: python or other tool to extract version information from JD Edwards binaries if availableAffected if Installed version falls within 9.2.0.0 through 9.2.26.2 inclusive
-
Verify JDENET service statusCheck if JDENET (JD Edwards NETwork) service is running. Look for processes named jdenet, jde.ini configuration file containing JDENET settings, or netstat entries on typical JDENET ports (internal ports vary but commonly 6000-9000 range)Affected if JDENET protocol service is active and listening for network connections
-
Assess network exposure of JDENETReview firewall rules, network configurations, and ACLs to determine if JDENET ports are accessible from untrusted networks. Check if the host is directly exposed to the internet or has open ingress on ports used by JDENETAffected if JDENET ports are accessible from untrusted or external network segments without proper access controls
The environment is affected if JD Edwards EnterpriseOne Tools version 9.2.0.0 through 9.2.26.2 is installed AND the JDENET network protocol is exposed, allowing unauthenticated attackers to reach the vulnerable component.
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 available security patch for this vulnerability immediately. Additionally, restrict network access to JDENET ports and implement defense-in-depth controls around JD Edwards systems until patching is complete.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46882 — 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-46882 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