Quick answers
- Is CVE-2026-46817 exploited in the wild?
- Yes. CVE-2026-46817 is known to be exploited in the wild, first recorded on 15 July 2026. Treat it as urgent.
- How severe is CVE-2026-46817?
- Critical severity, with a CVSS score of 9.8, published 28 May 2026.
- Which products and versions are affected?
- Oracle Payments 12.2.3 - 12.2.15, 12.2.3-12.2.15.
- Is there a fix for CVE-2026-46817?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-46817 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-46817?
- Check whether you run Oracle E-Business Suite or Oracle Payments at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This vulnerability is classified as Improper Privilege Management (CWE-269) and Missing Authentication for Critical Function (CWE-306) within the File Transmission component of Oracle Payments. The flaw is easily exploitable via HTTP without requiring any user interaction or prior authentication. A successful exploit allows a remote attacker to achieve full compromise of the Oracle Payments product, impacting confidentiality, integrity, and availability. The vulnerability affects Oracle E-Business Suite versions 12.2.3 through 12.2.15. Oracle has addressed this issue in their May 2026 security alert.
Affected products
- Oracle E-Business Suite (Oracle Payments) 12.2.3 - 12.2.15
Timeline
- 2026-05-28: disclosed: Initial disclosure by Oracle
- 2026-05-28: advisory: NVD publication date
- 2026-06-17: other: Last modified date in NVD record