CVE-2026-46913
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: Installation Security). Supported versions that are affected are 9.2.0.0-9.2.26.2. Easily exploitable vulnerability allows unauthenticated attacker with logon to the infrastructure where JD Edwards EnterpriseOne Tools executes to compromise JD Edwards EnterpriseOne Tools. While the vulnerability is in JD Edwards EnterpriseOne Tools, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of JD Edwards EnterpriseOne Tools. CVSS 3.1 Base Score 9.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/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 · moderate confidenceOracle JD Edwards EnterpriseOne Tools contains a vulnerability in the Installation Security component affecting versions 9.2.0.0 through 9.2.26.2. The vulnerability is locally exploitable (AV:L) with low attack complexity and requires no privileges (PR:N), allowing an attacker with logon access to the infrastructure to achieve complete takeover (C:H/I:H/A:H) of the JD Edwards application. The scope change (S:C) indicates the attack may impact additional Oracle products beyond the primary target.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/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 installationLocate the JD Edwards EnterpriseOne Tools installation on the system using Oracle administrative utilities or by checking common installation directoriesAffected if Oracle JD Edwards EnterpriseOne Tools is installed on the system
-
Determine installed version numberQuery the installed version using Oracle enterprise management tools or check version metadata files within the JD Edwards installation directoryAffected if The installed version is between 9.2.0.0 and 9.2.26.2 inclusive
-
Confirm Installation Security component is presentCheck if the Installation Security component is configured within the JD Edwards EnterpriseOne Tools environment using Oracle administrative interfacesAffected if The Installation Security component is enabled or configured in the environment
-
Review access to the underlying infrastructureAudit user accounts and access permissions to the server or infrastructure where JD Edwards EnterpriseOne Tools is installedAffected if Multiple user accounts have local logon access to the infrastructure hosting the application
The environment is affected if Oracle JD Edwards EnterpriseOne Tools version 9.2.0.0 through 9.2.26.2 is installed with the Installation Security component present and the underlying server is accessible to users beyond the intended administrative scope.
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 applicable patch for this vulnerability (refer to Oracle Critical Patch Update). As a compensating control, strictly limit and monitor access to the infrastructure where JD Edwards EnterpriseOne Tools is installed to reduce the attack surface.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46913 — 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-46913 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