CVE-2026-46911
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 Project Costing product of Oracle JD Edwards (component: Job Costing). The supported version that is affected is 9.2. Easily exploitable vulnerability allows low privileged attacker with network access via JDENET to compromise JD Edwards EnterpriseOne Project Costing. While the vulnerability is in JD Edwards EnterpriseOne Project Costing, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all JD Edwards EnterpriseOne Project Costing accessible data as well as unauthorized access to critical data or complete access to all JD Edwards EnterpriseOne Project Costing accessible data. CVSS 3.1 Base Score 9.6 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N).
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 vulnerability in the Job Costing component of JD Edwards EnterpriseOne Project Costing version 9.2 allows authenticated attackers with low privileges and network access via JDENET to create, delete, modify, or read critical data. The CVSS scope change indicates exploitation may impact additional JD Edwards products beyond Project Costing.
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.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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
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 Oracle JD Edwards EnterpriseOne installationLocate JD Edwards installation directory (typically under $JDEDWARDS_HOME or C:\Oracle\JD Edwards), check for EnterpriseOne folder structure, or query Windows services for 'Oracle JD Edwards' servicesAffected if JD Edwards EnterpriseOne software is found on the system
-
Verify installed EnterpriseOne versionCheck the JDEPLAN.TXT or version.info file in the installation path, or access EnterpriseOne About page (NATIVE_OS400 or through JDE HTML server), or run 'jde.ini' version sectionAffected if Version is exactly 9.2
-
Confirm Job Costing module is enabledAccess EnterpriseOne World/UGBU, check Module/Application Manager for P510131 (Job Cost Setup) or P5101 (Job Cost Entry) applications, or query the F984051 table for Job Costing module presenceAffected if Job Costing module (Project Costing) is present and accessible in the menu
-
Check JDENET network exposureReview network configuration for JDENET listener ports (typically 6009, 6010, or custom ports defined in jde.ini under [JDENET]), scan external-facing interfaces for these ports using 'netstat -an' or port scannerAffected if JDENET ports are listening on non-internal network interfaces or exposed externally
-
Audit Job Costing user access privilegesQuery F0092 (User/Role Security) table or check through Security Console for users with access to Job Costing (P5101/P510131), verify if low-privileged users have Create/Update/Delete permissions on these applicationsAffected if Users with low-privilege roles (e.g., *USER) have Create/Update/Delete access to Job Costing functions
System is affected if Oracle JD Edwards EnterpriseOne version 9.2 is installed with Job Costing module enabled and JDENET is network-accessible, particularly if low-privileged users have access to Job Costing functions.
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 Oracle Critical Patch Update for CVE-2026-46911. Until patches are available, restrict network access to JDENET ports and enforce least-privilege access controls for Project Costing users.
- 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-46911 — 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-46911 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