CVE-2026-87325 Oracle Corporation CVE debrief

Who should care

Defenders responsible for JD Edwards EnterpriseOne Tools, security teams, and IT administrators should assess exposure and potential impact of this vulnerability. Additionally, operators managing JD Edwards EnterpriseOne Tools deployments, platform administrators, and vulnerability management teams should also be aware of the potential risks and take necessary actions to mitigate them.

Why it matters

Defenders should care about CVE-2026-87325 as it allows low privileged attackers to compromise JD Edwards EnterpriseOne Tools, potentially leading to unauthorized data access and system crashes, requiring verification of exposure and impact.

• Potential unauthorized data access
• Possible system crashes (complete DOS)
• Unauthorized update, insert or delete access to some data
• Unauthorized read access to a subset of data

Technical summary

The vulnerability in JD Edwards EnterpriseOne Tools product of Oracle JD Edwards (component: Enterprise Infrastructure SEC) allows low privileged attacker with network access via JDENET to compromise JD Edwards EnterpriseOne Tools. Successful attacks can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of JD Edwards EnterpriseOne Tools as well as unauthorized update, insert or delete access to some of JD Edwards EnterpriseOne Tools accessible data and unauthorized read access to a subset of JD Edwards EnterpriseOne Tools accessible data.

Defensive priority

Defenders should prioritize verifying exposure of JD Edwards EnterpriseOne Tools versions 9.2.0.0-9.2.26.5 and assessing the impact of potential unauthorized data access and system crashes.

Recommended defensive actions

• Verify JD Edwards EnterpriseOne Tools versions 9.2.0.0-9.2.26.5 are in use and assess exposure
• Assess potential impact of unauthorized data access and system crashes
• Review and implement compensating controls to mitigate potential attacks
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, its impacts, and affected versions. However, the corpus does not establish remediation or exploitation details, requiring verification from official sources.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.