Oracle E-Business Suite Improper Privilege Management Vulnerability (CVE-2026-46817)
Published Last modified In CISA KEV since Sources: CVE.org, SingCERT, pwn.watch, EUVD, BSI
What is affected, what to do
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.
The vulnerability is being actively exploited; treat it as a priority. The available sources name no fixed version. Check the vendor guidance in the references below. Immediate actions, mitigation and detection rules are in the runbook below.
- Affected
- Oracle Payments
lte 12.2.3..12.2.15
- Oracle Payments
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
9.8
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: NVD, CVSS v3
9.8
CVSS v3
Severity Critical on the scale from 0 to 10.
Source: CVE.org, SingCERT, pwn.watch, EUVD, BSI
12.3 %
EPSS score
Elevated — model estimates 10-50% exploitation likelihood.
Source: FIRST EPSS, percentile 96.2
Show all metrics
- Severity
- Critical
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 241.07 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- actively exploitedSource: VulnCheck KEV (opens in a new tab) How we classify
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 9.8 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 9.8
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 12.3 %
- Elevated — model estimates 10-50% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 96.2
- Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- Actively exploited
- Published
In CISA KEV since
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- CISA assessment (SSVC)
- Exploitation: active · automatable · Technical impact: total
- Source: CISA Vulnrichment, as of 15 July 2026
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-306, CWE-287, CWE-269
Response and mitigation
Why act now?
Prioritisation rationale
This flaw needs no authentication and no user interaction, is reachable over HTTP, and hands the attacker full control of Oracle Payments. That makes it directly business-critical, because tampered payment files or bank details translate into immediate financial loss. Oracle EBS estates are a recurring target for data theft and extortion. KEV inclusion confirms real-world exploitation even though the model-based exploitation likelihood currently looks only moderate. CISA does not flag known ransomware use, which does not lower the urgency for extortion scenarios that involve no encryption. Treat internet-facing EBS instances as an emergency change within 24 hours and internal-only instances in the next expedited patch window. NIS2/KRITIS entities should assess reporting obligations if any indicators of compromise surface.
Runbook step 1
Immediate response (0-24 h)
- Establish exposure: Inventory every Oracle E-Business Suite instance on 12.2.3 through 12.2.15, including test, clone and DR environments. Confirm whether the HTTP(S) entry point (Oracle HTTP Server or WebLogic managed servers) is reachable from the internet or from partner networks. Flow Manufacturing (12.2.9+) and Public Sector Financials (12.2.6+) are explicitly in scope.
- Patch: Apply the Oracle Payments (File Transmission component) fix from the relevant Oracle Critical Patch Update. A patch is available from the vendor; look up the exact patch ID and CPU release in the Oracle advisory or My Oracle Support. Check prerequisites first (AD/TXK code level,
adoponline patching cycle). - Cut external access now: Until the patch is in, block internet access to the EBS web tier at the perimeter, or allow it only through VPN/ZTNA with upstream authentication. Prioritise external iSupplier/iRecruitment DMZ nodes.
- Assume breach on exposed systems: For internet-facing instances, preserve evidence from the start of exposure (OHS access logs, WebLogic logs,
$APPLRGF, database audit trail). Then hunt using the detection rules below. - Protect the payment run: Alert accounts payable and treasury. Before the next payment release, use four-eyes verification on recently changed supplier bank accounts and outbound payment files.
- Rotate credentials if anything looks off: Rotate the APPS/SYSADMIN passwords, the bank transmission credentials (SFTP keys and certificates used by Payments file transmission) and the WebLogic admin passwords.
Runbook step 2
Mitigation layers
- Network segmentation: Put the EBS application tier in a dedicated zone. Allow ingress only from the reverse proxy or WAF. Restrict egress to explicitly required destinations (bank SFTP endpoints, mail relay) and deny everything else, which blocks tool staging and exfiltration.
- WAF/reverse proxy: Deny external requests to
/OA_HTML/paths tied to Oracle Payments (product prefixiby), or restrict them to known source IPs. Also block oversized POST bodies, XML/XSLT payloads and serialisation patterns aimed at EBS servlets. Prefer an allowlist of externally required responsibilities and URLs over a blocklist. - Feature reduction: If Payments file transmission is not used, disable the related functions or servlets, or block them via OHS
Locationdirectives. Restrict DMZ nodes with the "External" node trust level. - Endpoint hardening: Make EDR mandatory on application-tier hosts. Block, or at least alert on, shell spawns from the WebLogic/Java processes (
oacore,oafm,forms). Add file integrity monitoring on$OA_HTMLand$COMMON_TOP. - IAM/least privilege: Review Payments administrator responsibilities and reduce them to the minimum. Enforce approval workflows for changes to supplier bank accounts and payment process profiles.
Runbook step 3
Detection rules
- Web access logs (OHS/proxy): Look for unauthenticated hits on Payments-related paths, for example:
index=web host=ebs* uri_path="/OA_HTML/*" (uri_path="*iby*" OR uri_path="*Iby*") | stats count by src_ip, uri_path, status, http_method. Flag external sources, POST bursts, and HTTP 200 responses with no preceding login flow (/OA_HTML/AppsLogin). - EDR process ancestry: Watch for the EBS managed-server Java process spawning
sh,bash,curl,wget,perlorpython. Sigma shape:ParentImage|endswith: '/java'ANDImage|endswith: ['/sh','/bash','/curl','/wget']ANDUser: applmgr(or your EBS OS user). The auditd equivalent is-a always,exit -F arch=b64 -S execve -F uid=<applmgr-uid>. - Network telemetry (Zeek/Suricata): Alert on new outbound connections from the EBS app tier to unapproved destinations, especially HTTP(S) to newly registered domains or reverse-shell patterns on unusual ports. Also flag transfers to bank SFTP targets outside scheduled payment runs.
- Database/application audit: Watch for unexpected changes to
IBY_EXT_BANK_ACCOUNTS, payment process profiles or transmission configuration. Also flag newFND_USERrows or responsibility grants without a change ticket. Enable Unified Auditing on these objects and ship the results to the SIEM. - File system: New or modified
.jsp,.classor.xslfiles under$OA_HTMLor WebLogic deployment directories may indicate a webshell. Unknown files in the payment-file output directory are also suspicious.
- Web access logs (OHS/proxy): Look for unauthenticated hits on Payments-related paths, for example:
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
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).
Source: CISA KEV Catalog, NVD (NIST), CVE.org (MITRE), CSA/SingCERT, pwn.watch, ENISA EUVD, cvelistv5, BSI WID Portal, BSI CSAF
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| Oracle Corporation | Oracle Payments |
|
|
| oracle | e-business_suite |
|
|
| Oracle | E-Business Suite |
|
|
Vendors and products
Weakness classes (CWE)
CWE-306Missing Authentication for Critical Function
Base
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
Entry at MITRE CWE-306CWE-287Improper Authentication
Class
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
Entry at MITRE CWE-287CWE-269Improper Privilege Management
Class
The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
Entry at MITRE CWE-269
Public exploit references
Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.
| CISA KEV Catalog | CISA Known Exploited Vulnerability (opens in a new tab)cisa.gov | actively exploited | |
| PoC-in-GitHub (nomi-sec) | CVE-2026-46817 (opens in a new tab)github.com | PoC (publicly reported)reported, not verified | |
| PoC-in-GitHub (nomi-sec) | CVE-2026-46817 (opens in a new tab)github.com | PoC (publicly reported)reported, not verified |
References & sources
- oracle.comOracle Advisoryeuvd, Vendor advisory, pwn-watch
- cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2026-46817government-resource
- pwn.watchpwn.watch: Oracle E-Business Suite: Oracle E-Business Suite Improper Privilege Management Vulnerabilitypwn-watch
- NVD (NIST)NVD: CVE-2026-46817pwn-watch
- cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
CISA KEV entry updated9119a7d8…
4 individual changes: Date Added, Due Date, Required Action, Vulnerability Name
Show 4 original changes
Individual changes of this event as published by NVD Type Action Before After Date Added added —2026-07-15Due Date added —2026-07-15Required Action added —2026-07-15Vulnerability Name added —2026-07-15Source identifier: 9119a7d8-5eab-497f-8521-727c672e3725
Record modifiedCISA ADP
CISA assessment (SSVC): exploitation: active, automatable: yes
Show 2 original changes
Individual changes of this event as published by NVD Type Action Before After Reference added —https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-46817SSVC assessment changed {"id":"CVE-2026-46817","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-05-29T15:41:43.972022Z"}{"id":"CVE-2026-46817","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-07-15T17:34:21.994251Z"}Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
One NVD translation into another language is hidden.
Linked advisories
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-46817"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-46817.svg?lang=en" alt="CVE-2026-46817 – NEOSEC Intel" height="20"></a>