CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Called exploited 32 days after disclosure.
Measured from the CVE publication date to the earliest of 3 KEV catalogues that list it.
The life of this vulnerability
- CVE published
- First KEV listing32d
- Last KEV listing16d
- Last sighting23d
Gaps are compressed to equal steps. The elapsed time is printed under each.
Which catalogues call it exploited
- CISA KEVUS federallisted Jul 15, 2026
- EUVDENISA, European Unionlisted Jul 15, 2026
- VulnCheck KEVcommercial researchlisted Jun 29, 2026
- CIRCLaggregator, mirrors the abovelisted Jun 29, 2026, not counted
3 catalogues list it. CIRCL aggregates the others and is shown but not counted.
Public exploitation evidence
- reported exploitationwww.recordedfuture.com/blog/july-2026-cve-landscape
- reported exploitationwww.cisa.gov/sites/default/files/feeds/known_exploited_vulne
- reported exploitationwww.recordedfuture.com/blog/june-2026-cve-landscape
- reported exploitationwww.guidepointsecurity.com/wp-content/uploads/2026/07/GRIT_Q
- reported exploitationx.com/Shadowserver/status/2072267510439686276#m
- reported exploitationx.com/helpnetsecurity/status/2071957315360522651
8 public reports collected from VulnCheck and CIRCL, first on Jun 29, 2026. Each links to its original source. We have not verified them.
Description
Vulnerability in the Oracle Payments product of Oracle E-Business Suite (component: File Transmission). Supported versions that are affected are 12.2.3-12.2.15. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Payments. Successful attacks of this vulnerability can result in takeover of Oracle Payments. CVSS 3.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
Required action (CISA)
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

