Oracle lists supported EBS releases 12.2.3 through 12.2.15 as affected. Its November 2026 risk matrix rates the flaw Critical at CVSS 3.1 9.8.Oracle says an attacker with network access can exploit the HTTP path without credentials or user interaction and take over the affected component. Horizon3 researchers describe the flaw as remote code execution on the EBS application tier. Their analysis also describes a chain with the separate authorization bypass CVE-2026-114924.
What it allows
How Does CVE-2026-114925 Lead to Code Execution?
Horizon3's patch analysis places the flaw in an Oracle Applications Framework REST Services request handler. The researchers say the handler instantiates Java classes named by request input without limiting the permitted classes. They assess that this behavior can become operating system command execution on the EBS application tier.
Horizon3 also describes a chain with CVE-2026-114924, an authorization bypass in Oracle Application Object Library Core. According to the researchers, the bypass exposes protected REST functions, and the REST Services flaw then enables command execution. Oracle lists the two CVEs in separate components, each with a 9.8 score. The chain is Horizon3's assessment, not an Oracle risk-matrix claim.
What Is the Exploitation Status of CVE-2026-114925?
The CISA KEV catalog snapshot dated 18 November 2026 did not list CVE-2026-114925. That catalog status is a dated prioritization signal, not a verdict on any particular EBS server. The profile therefore records exploitation as unknown.
Oracle's network and authentication ratings justify prompt action on reachable EBS systems. An internet-facing tier is especially accessible, while Horizon3 notes that internal or partner network reachability also matters. Review the November Oracle patch priority overview for the wider update.
Who is affected
Which Oracle EBS Installations Are Affected?
Oracle lists supported EBS 12.2.3 through 12.2.15 for this REST Services issue. The risk matrix marks HTTP as remotely exploitable without authentication, privileges or user interaction. Oracle says an HTTP listing includes the protocol's secure variant, so HTTPS alone does not remove the exposure.
The advisory directs EBS administrators to My Oracle Support Note KA923 for patch availability and installation instructions. Its public risk matrix supplies no single fixed EBS release number. Verify the installed November 2026 patch for this CVE instead of treating 12.2.15 as fixed. Oracle also recommends updating Database and Fusion Middleware components used by EBS.
How Should Teams Verify the Oracle EBS Patch?
Inventory each running EBS application tier, installed release and reachable network segment. Obtain the applicable November 2026 patch identifiers from Oracle's EBS patch availability document. Apply the prescribed updates and record the installation result for each environment.
After maintenance, confirm that each running tier has the relevant patch installed and validate normal EBS operation. Put that evidence into the patch management process. Review web access and application logs against local baselines if an exposed tier was unpatched.
Until patching is complete, restrict reachability from untrusted segments and test any protocol restriction before production use. Oracle warns that blocking required protocols can break functionality and does not correct the flaw. External attack surface management can help inventory public EBS exposure; assess internal and partner paths separately.
Timeline
- 2026-11-17
Oracle published its November 2026 Critical Security Patch Update, including CVE-2026-114925.
- 2026-11-17
The NVD record for CVE-2026-114925 was published.
- 2026-11-18
The CISA KEV catalog snapshot checked for this profile did not list CVE-2026-114925.
What to do
-
Inventory EBS application tiers
Identify running EBS 12.2.3 through 12.2.15 installations, their REST Services exposure, reachable segments and installed November 2026 patches.
-
Apply Oracle's EBS patch
Use My Oracle Support Note KA923 to select and install the November 2026 patch that addresses CVE-2026-114925.
-
Verify the running installation
Confirm the prescribed patch identifier on every running application tier after maintenance. Validate EBS operation; the EBS release number alone does not prove remediation.
-
Reduce reachability while patching
Restrict web tier access from untrusted network segments, test changes and review access logs against local baselines. This measure does not replace patching.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-114925 in Brandefense Atlas
The Atlas record of CVE-2026-114925: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Can CVE-2026-114925 be reached without credentials?
Yes. Oracle marks the HTTP path remotely exploitable without authentication, privileges or user interaction when an attacker can reach the affected EBS tier.
How does CVE-2026-114925 relate to CVE-2026-114924?
Oracle lists them as separate REST Services and Application Object Library flaws. Horizon3 says chaining the authorization bypass with this flaw can lead to command execution.
Is EBS 12.2.15 already fixed?
A release number is insufficient. Oracle includes 12.2.15 in the affected range and directs customers to My Oracle Support Note KA923 for the applicable patch.
Does HTTPS prevent exploitation?
No. Oracle says an HTTP entry in its risk matrix includes secure variants. Apply the patch and restrict reachability while maintenance is pending.