Threats / Oracle / CVE-2026-46817
CVE-2026-46817
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-07-16
Oracle E-Business Suite vulnerability
Oracle E-Business Suite contains an improper privilege management vulnerability that allows an unauthenticated attacker with network access via HTTP to compromise Oracle Payments. Successful attacks of this vulnerability can result in takeo
Verdict
Today item — known-exploited.
Confirmed exploited in the wild (CISA KEV). Prioritize remediation now and verify exposure.
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
7 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-07-15).
Probability (EPSS)
EPSS 0.00677 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Oracle, E-Business Suite. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-269 Improper Privilege Management, CWE-287 Improper Authentication, CWE-306 Missing Authentication — weakness family: Authorization / access control, Authentication.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
WeaknessCWE-269 · Improper Privilege ManagementCWE-287 · Improper AuthenticationCWE-306 · Missing AuthenticationAuthorization / access control, Authentication
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then boardAttacker/business narrative framing is pending triage for this record — see Coverage & confidence below. Facts and verdict above are derived deterministically from the public feed.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05