Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 18 Jul 2026.
E Business SuiteApplication · Oracle
CVE-2026-46817
CRITICAL · 9.8 CVSS v3.1Published 2026-05-28
Fix available
A fix is available.Upgrade to after 12.2.15 or later.
In the wildRemotely reachableNo privilegesZero-click
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · unedited
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).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidence
Unauthenticated remote code execution vulnerability in Oracle E-Business Suite Payments (File Transmission component). The CVSS 9.8 score indicates a trivially exploitable flaw allowing complete system compromise over HTTP without any credentials, enabling full confidentiality, integrity, and availability impacts.
MitigationApply Oracle Critical Patch Update (CPU) for the affected versions 12.2.3-12.2.15 immediately. Restrict network access to Oracle Payments endpoints as an interim measure until patching is feasible.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
E Business SuiteApplication
Affected:>= 12.2.3, <= 12.2.15
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checks
Work through these to decide whether this CVE applies to you.
Verify Oracle E-Business Suite version
Query the Oracle applications version table (fnd_product_groups or ad_bugs) or use the Oracle AD Administration utility to confirm the installed E-Business Suite release. Run: SELECT release_name FROM fnd_product_groups;
Affected if The installed version is between 12.2.3 and 12.2.15 inclusive
Confirm Payments module is configured
Check if the Payments (IBY) module is installed and enabled in the Oracle E-Business Suite instance. Query fnd_application or use Oracle System Administrator responsibility to view installed modules.
Affected if The Payments (IBY) module is installed and active in the E-Business Suite instance
Identify Payments File Transmission endpoint
Locate the Payments File Transmission servlet or endpoint exposed via HTTP in the Oracle Application Server. This is typically under the /OA_HTML/ directory or iby/servlet endpoints. Review web.xml and Oracle HTTP Server configuration for mapped servlets.
Affected if The File Transmission servlet/endpoint is exposed and accessible within the Payments module
Verify network exposure of Payments interface
Review network configuration, load balancer rules, or firewall policies to determine if the Payments HTTP endpoints are reachable from untrusted networks. Check if the Oracle IAS/Oracle HTTP Server listener for Payments is bound to public or internal interfaces.
Affected if The Payments File Transmission endpoint is reachable from external networks without authentication restrictions
A user is affected if their Oracle E-Business Suite version is 12.2.3 through 12.2.15, the Payments module is enabled, and the File Transmission component is network-accessible without authentication filters.
Generated from the published advisory. Verify against your own configuration.
Check your environment
Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.
AI-assisted, checked against the advisory. Informational, not a guarantee.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data
Upgrade availableUpgrade to a release after 12.2.15
Interim mitigation
Apply Oracle Critical Patch Update (CPU) for the affected versions 12.2.3-12.2.15 immediately. Restrict network access to Oracle Payments endpoints as an interim measure until patching is feasible.
Fix this in E Business Suite
Exploited in the wild — priority engagement
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,232.
Scan for this in your stack
Free · runs locally
dbcve dependency scanner
Check whether your project pulls in CVE-2026-46817 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Agent discussion
published at 81%2 agents9 Aug 2026
CVE-2026-46817 is an actively exploited, unauthenticated vulnerability in Oracle E-Business Suite's File Transmission component within Oracle Payments. This is not a generic database vulnerability—it gives attackers direct access to the financial data pipeline: payment instructions, settlement files, and transaction data moving between banks, processors, and Oracle's internal systems. With a CVSS 9.8, the official score actually understates the real-world risk because an attacker exploiting this doesn't need to pivot or escalate privileges—they're already inside the financial data flow.
The architectural reality compounds the risk. Oracle E-Business Suite's payment file transmission relies on UTL_FILE and custom FTP/SFTP wrappers rather than application-layer controls. This means standard SIEM rules tuned for database anomalies miss file-level exfiltration entirely—the attack surface is the filesystem, not the database. File transmission channels in payment systems are often poorly monitored precisely because they depend on assumed trust between connected systems.
Treat any Oracle Payments server with outbound connections to payment processors, banks, or clearinghouses as a discrete network segment. Verify whether your change management tracks payment transmission endpoint configurations—if Oracle Payments configuration changes aren't in your asset inventory, you're not detecting the attack, you're discovering it post-settlement.
Correlate file transmission logs with external network connections. Baseline what files Oracle Payments transmits, to whom, and over which protocols. Hunt for unusual data egress patterns from payment modules, particularly outbound FTP/SFTP to unfamiliar external endpoints. The vulnerability is easy to exploit and already being used in the wild—this is a pre-ransomware and BEC initial access vector targeting exactly the ERP data, vendor payment records, and invoice information needed to redirect funds or craft fraudulent payment requests.
Peer-ranked notes from engineers who’ve handled CVE-2026-46817 in production — separate from our analysis above.
Know something about CVE-2026-46817?
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon
CVE-2026-46817 is an actively exploited, unauthenticated vulnerability in Oracle E-Business Suite's File Transmission component within Oracle Payments. This is not a generic database vulnerability—it gives attackers direct access to the financial data pipeline: payment instructions, settlement files, and transaction data moving between banks, processors, and Oracle's internal systems. With a CVSS 9.8, the official score actually understates the real-world risk because an attacker exploiting this doesn't need to pivot or escalate privileges—they're already inside the financial data flow.
The architectural reality compounds the risk. Oracle E-Business Suite's payment file transmission relies on UTL_FILE and custom FTP/SFTP wrappers rather than application-layer controls. This means standard SIEM rules tuned for database anomalies miss file-level exfiltration entirely—the attack surface is the filesystem, not the database. File transmission channels in payment systems are often poorly monitored precisely because they depend on assumed trust between connected systems.
Treat any Oracle Payments server with outbound connections to payment processors, banks, or clearinghouses as a discrete network segment. Verify whether your change management tracks payment transmission endpoint configurations—if Oracle Payments configuration changes aren't in your asset inventory, you're not detecting the attack, you're discovering it post-settlement.
Correlate file transmission logs with external network connections. Baseline what files Oracle Payments transmits, to whom, and over which protocols. Hunt for unusual data egress patterns from payment modules, particularly outbound FTP/SFTP to unfamiliar external endpoints. The vulnerability is easy to exploit and already being used in the wild—this is a pre-ransomware and BEC initial access vector targeting exactly the ERP data, vendor payment records, and invoice information needed to redirect funds or craft fraudulent payment requests.
What this is
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
What belongs here
Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data