CVE-2026-46910
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 HTTP to compromise JD Edwards EnterpriseOne Tools. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all JD Edwards EnterpriseOne Tools accessible data and unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of JD Edwards EnterpriseOne Tools. CVSS 3.1 Base Score 9.1 (Confidentiality and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 confidenceUnauthenticated remote vulnerability in JD Edwards EnterpriseOne Tools (Enterprise Infrastructure Security component) allows attackers with network HTTP access to compromise the system. Supported versions 9.2.0.0 through 9.2.26.2 are affected. Successful exploitation grants unauthorized access to critical data or complete denial of service.
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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 installationLocate the JD Edwards EnterpriseOne Tools installation directory or check system inventory for Oracle JD Edwards EnterpriseOne Tools components. Look for the Enterprise Infrastructure Security component in the installation.Affected if JD Edwards EnterpriseOne Tools is installed with the Enterprise Infrastructure Security component present
-
Determine installed versionCheck the installed version of JD Edwards EnterpriseOne Tools against the affected range. This may be found in installation logs, the Oracle Enterprise Manager, or version information files within the Tools installation directory.Affected if Installed version falls within 9.2.0.0 through 9.2.26.2 inclusive
-
Assess HTTP network exposureDetermine if the system has accessible HTTP endpoints exposed to the network. Review firewall rules, load balancer configurations, or web server settings that control external HTTP access to JD Edwards applications.Affected if HTTP endpoints are accessible from untrusted network segments or the internet
-
Verify Enterprise Infrastructure Security configurationCheck the configuration and enabled state of the Enterprise Infrastructure Security component within the JD Edwards EnterpriseOne Tools deployment. Review security policy settings for this component.Affected if Enterprise Infrastructure Security component is installed and active
A user is affected if their environment runs JD Edwards EnterpriseOne Tools version 9.2.0.0 through 9.2.26.2 with the Enterprise Infrastructure Security component enabled and HTTP network access exposed.
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.
dbcve · scopedApply Oracle Critical Patch Update for JD Edwards EnterpriseOne Tools. Until patch is applied, restrict network access to HTTP endpoints and implement additional authentication/segmentation controls.
9.2.27.0 or later (next quarterly patch set after 9.2.26.2)
- Identify the current JD Edwards EnterpriseOne Tools version in your environment
- Download and review the Oracle JD Edwards EnterpriseOne Tools patch for the January 2026 Critical Patch Update from Oracle Support (support.oracle.com)
- Apply the patch in a non-production environment first to validate compatibility
- Test critical business workflows after applying the patch
- Deploy the patch to production environments during a scheduled maintenance window
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing16.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,576.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46910 — 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-46910 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