CVE-2026-46903
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: Business Logic Infrastructure Security). Supported versions that are affected are 9.2.0.0-9.2.26.2. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP 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 8.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/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 vulnerability in JD Edwards EnterpriseOne Tools' Business Logic Infrastructure Security component allows low-privileged attackers with network access via HTTP to potentially take over the application. The CVSS 8.8 score reflects high impact across confidentiality, integrity, and availability.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 installed JD Edwards EnterpriseOne Tools versionLocate the JD Edwards EnterpriseOne Tools installation and retrieve the version number from the installation directory, enterprise server, or via the JD Edwards Administrator tool. Common locations include the installation log files or the 'System Installation' information within the JD Edwards EnterpriseOne management console.Affected if The installed version falls within the range 9.2.0.0 through 9.2.26.2 inclusive.
-
Confirm network accessibility of JD Edwards HTTP interfacesDetermine if the JD Edwards EnterpriseOne web interfaces (HTML Gateway, XML Dispatcher, or similar HTTP-based endpoints) are exposed to untrusted networks. Review firewall rules, load balancer configurations, or reverse proxy settings that govern external access to JD Edwards HTTP ports.Affected if HTTP interfaces are accessible from untrusted network segments or the public internet.
-
Review user account privilege levelsExamine the JD Edwards EnterpriseOne user role assignments and privilege configurations. Identify accounts with low-level privileges that have network access to the JD Edwards interfaces. Check role definitions within JD Edwards Security Console to determine which authenticated users can access the Business Logic Infrastructure Security component.Affected if Low-privileged user accounts exist with network access to JD Edwards HTTP interfaces.
-
Verify Business Logic Infrastructure Security component is in useDetermine if the Business Logic Infrastructure Security component is enabled or configured within the JD Edwards EnterpriseOne environment. This may be identified through the JD Edwards EnterpriseOne Configuration Manager, Security Server settings, or by reviewing deployed enterprise application configurations.Affected if The Business Logic Infrastructure Security component is active and accessible via network HTTP interfaces.
A user is affected if their JD Edwards EnterpriseOne Tools installation version is 9.2.0.0 through 9.2.26.2, the HTTP-based interfaces are network-accessible, and low-privileged authenticated users can reach the Business Logic Infrastructure Security 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 the relevant Oracle patch or upgrade to a non-vulnerable version (beyond 9.2.26.2). Thorough testing in a non-production environment is recommended before deployment.
- Consultation6.0 h
- Implementation12.0 h
- Testing16.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,944.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46903 — 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-46903 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