Oracle lists supported EBS versions 12.2.3 through 12.2.15 as affected. An unauthenticated attacker with network access over HTTP could take over the affected component.Oracle rates the flaw Critical at CVSS 3.1 9.8. Horizon3 researchers say this bypass can be chained with CVE-2026-114925, a separate REST Services flaw, to execute commands on the EBS application tier. This profile describes the authorization bypass; the second CVE requires its own patch assessment.
What it allows
How Does CVE-2026-114924 Affect Oracle EBS Authorization?
Oracle Application Object Library supplies authorization functions used across EBS. Horizon3's patch analysis says CVE-2026-114924 lets a network attacker bypass those checks and reach protected EBS REST functions. Oracle's risk matrix labels the HTTP path remotely exploitable without authentication, privileges or user interaction.
Horizon3 says the bypass can expose the separate REST Services issue CVE-2026-114925. Its researchers describe the combined result as operating system command execution on the EBS application tier. That chain assessment belongs to Horizon3; Oracle lists the two CVEs as distinct vulnerabilities in different components.
What Is the Exploitation Status of CVE-2026-114924?
The available primary sources describe an attack path, not a verified incident affecting a named EBS deployment. The 18 November 2026 CISA KEV catalog snapshot did not list this CVE. A catalog status is a dated prioritization signal and cannot establish whether an individual server was attacked.
Prioritize reachable, unpatched EBS instances because Oracle assigns a 9.8 score and identifies an unauthenticated network route. Internet exposure increases reach, but Horizon3 notes that an attacker on a connected internal or partner network could also reach an EBS web tier. Review the related earlier Oracle EBS Application Object Library flaw separately; its CVE and patch history differ.
Who is affected
Which Oracle EBS Versions Are Affected by CVE-2026-114924?
Oracle lists supported Oracle E-Business Suite 12.2.3 through 12.2.15 for the Application Object Library Core issue. The risk matrix gives HTTP as the affected protocol, and Oracle says a listed protocol also includes its secure variants. EBS web access over HTTPS therefore does not remove the exposure.
The November 2026 Critical Security Patch Update supplies the fix. Oracle directs EBS customers to My Oracle Support Note KA923 for the applicable patch numbers and installation instructions. The public advisory does not provide a single fixed EBS version boundary, so verify the installed patch rather than relying on the release number alone.
How Should Administrators Verify the Oracle EBS Fix?
Inventory EBS application tiers and record each installed 12.2 release, exposed web tier and reachable network segments. Obtain the November 2026 EBS patch list from Oracle's patch availability document, then apply the relevant updates. Record the patch identifiers and installation results for each environment.
After maintenance, verify that the running application tier has the prescribed patches installed and that EBS functions still work. Oracle also recommends the November updates for Database and Fusion Middleware components used by EBS. Include those components in the patch management process.
If patching must wait, Oracle says blocking required network protocols may reduce risk, but it requires testing and is not a long term fix. Restrict reachability to the EBS web tier from untrusted segments and review application and access logs against local baselines. External attack surface management can support the public exposure inventory; internal and partner access still need separate review.
Timeline
- 2026-11-17
Oracle published its November 2026 Critical Security Patch Update, including a patch for CVE-2026-114924.
- 2026-11-17
The NVD record for CVE-2026-114924 was published.
- 2026-11-18
The CISA KEV catalog snapshot checked for this profile did not list CVE-2026-114924.
What to do
-
Inventory affected EBS tiers
Identify Oracle EBS 12.2.3 through 12.2.15 application tiers, their network reachability and their installed November 2026 security patches.
-
Apply the Oracle update
Use Oracle's November 2026 EBS patch availability document, My Oracle Support Note KA923, to select and install the applicable patches for this CVE.
-
Verify remediation
After maintenance, confirm the prescribed patch identifiers are installed on every running application tier and validate normal EBS operation. A release number alone is insufficient evidence.
-
Limit access while patching
Restrict EBS web tier access from untrusted networks and review access logs using local baselines. Test any protocol restrictions before production deployment.
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-114924 in Brandefense Atlas
The Atlas record of CVE-2026-114924: 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-114924 be reached without EBS credentials?
Yes. Oracle marks the HTTP issue remotely exploitable without authentication, privileges or user interaction when an attacker can reach the affected EBS web tier.
Is CVE-2026-114924 the same flaw as CVE-2026-114925?
No. Oracle assigns them to Application Object Library Core and Applications Framework REST Services respectively. Horizon3 says attackers can chain them.
Does upgrading to EBS 12.2.15 alone prove this issue is fixed?
No. Oracle lists 12.2.15 among affected supported versions. Administrators must verify the applicable November 2026 patch from Oracle's EBS patch availability document.
Does HTTPS prevent this bypass?
No. Oracle says that a protocol listed as HTTP in its risk matrix also includes secure variants. Restrict reachability and apply the patch.