Unauthenticated reading and modification of critical data
Published Aug 18, 2026 · Updated Aug 25, 2026
Access-control failure in Oracle Payments 12.2.3 through 12.2.15 allows remote attackers to read and modify critical data over HTTPS. Oracle identifies the locus as File Transmission but does not disclose the request, endpoint, or access-control operation that mishandles untrusted input. No credentials or user interaction are required, but exploitation has high complexity and affects confidentiality and integrity without interrupting service.
Summary
What happened
Access-control failure in Oracle Payments 12.2.3 through 12.2.15 allows remote attackers to read and modify critical data over HTTPS. Oracle identifies the locus as File Transmission but does not disclose the request, endpoint, or access-control operation that mishandles untrusted input. No credentials or user interaction are required, but exploitation has high complexity and affects confidentiality and integrity without interrupting service.
The record
- CVE
- CVE-2026-70699
- Published
- Aug 18, 2026
- Updated
- Aug 25, 2026
- Vendor
- Oracle Corporation
- Product
- Oracle Payments
- Classifications
- T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 18, 2026CVE publishedPublication date reported by the CVE source.
- Aug 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=12.2.3 <=12.2.15
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo