Skip to content
major vulnerability· requires attention

Affects widely used ERP software (JD Edwards Accounts Payable 9.2); high risk to financial data and processes; could disrupt IT/finance operations.

ERP

CVE-2026-46891

3.1
Low
EPSS 0.34%Patch availableJun 17, 2026

Low-privilege remote attacker can access/modify AP data via HTTP.

common questions

Is CVE-2026-46891 being exploited?

Not confirmed. CVE-2026-46891 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.34% probability of exploitation in the next 30 days.

How severe is CVE-2026-46891?

CVE-2026-46891 is rated Low with a CVSS score of 3.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-46891?

Yes. A fix has been recorded for CVE-2026-46891. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-46891 affect?

CVE-2026-46891 affects Oracle JD Edwards EnterpriseOne Accounts Payable 9.2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-46891?

Patch when available; restrict HTTP access; enforce least-privilege AP roles.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Oracle JD Edwards EnterpriseOne Accounts Payable 9.2
impact

Remote attacker with HTTP access can modify AP data or access AP data; confidentiality and integrity affected; no availability impact.

action required

Patch when possible

affected versions
Oracle Corporation JD Edwards EnterpriseOne Accounts Payable
  • affected9.2

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free