Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore
Security NewsNews Explainer

Oracle EBS November Patch Closes an Authorization Bypass and RCE Chain

The Oracle EBS November 2026 patch addresses two critical CVEs. Check affected 12.2 releases, apply both fixes, and verify the application tier.

By
Brandefense Research Team
Reviewed by
Brandefense Analyst Team
Published
20 November 2026
Reading time
3 min read
Layered enterprise application blocks with two repaired fractures inside a shield.

The Oracle EBS November 2026 patch addresses two critical flaws that Horizon3 says can be chained for unauthenticated code execution on the application tier. Oracle lists CVE-2026-114924 and CVE-2026-114925 in its November 17 Critical Security Patch Update. Organizations running E-Business Suite 12.2.3 through 12.2.15 should apply the EBS patches specified by Oracle for their installation.

Oracle rates each flaw 9.8 under CVSS 3.1 and lists HTTP access without authentication as the attack condition. The two CVEs affect different components, so treat them as separate patch items. A newer release number alone does not prove the November fixes are installed. A vulnerability intelligence platform can help organize the exposure and patch decision across the estate.

Oracle EBS November 2026 Patch: Which Systems Need It?

Oracle’s risk matrix identifies the affected supported releases and the two components below. It does not publish a single fixed EBS version for these CVEs. The EBS patch availability document linked from Oracle’s advisory is the installation-specific source for patch numbers.

CVE Affected EBS component and releases Fix to verify
CVE-2026-114924 Application Object Library, Core; 12.2.3 through 12.2.15 November 2026 EBS security patch for this CVE
CVE-2026-114925 Applications Framework, REST Services; 12.2.3 through 12.2.15 November 2026 EBS security patch for this CVE

Oracle also warns that EBS deployments can inherit exposure from their Oracle Database and Fusion Middleware components. Its EBS matrix excludes those component patches. Check their installed versions and apply the relevant November updates through the same change plan.

How Can the Two EBS Flaws Be Chained?

Horizon3’s November 19 analysis describes CVE-2026-114924 as an authorization bypass in the shared Application Object Library layer. According to the researchers, that bypass can expose protected REST functions. They describe CVE-2026-114925 as a flaw in a REST request handler that can lead to command execution on the EBS application tier.

In Horizon3’s analysis, combining the bypass with the REST flaw removes the credential requirement for the code execution path. Oracle’s matrix separately marks both flaws as remotely exploitable without authentication over HTTP. Network reachability matters even when EBS is not public: an internal or partner network path to the web tier can still expose the service.

Oracle gives both CVEs high confidentiality, integrity and availability impact under CVSS 3.1. The NVD records available November 19 do not include CVSS 4.0 scores. CISA’s November 18 KEV catalog did not list either CVE; that catalog status is not a finding about any individual deployment.

What Should EBS Owners Check and Patch First?

Inventory EBS installations, identify their 12.2 release, and document who can reach the application web tier. Prioritize reachable systems, then use Oracle’s EBS patch availability document to select the correct patches for both CVEs.

EBS November patch verification
  • Record each EBS release and application tier owner.
  • Check the Oracle patch document for both CVEs and required dependencies.
  • Apply the EBS, Database and Fusion Middleware patches relevant to that installation.
  • Confirm installed patch identifiers and test the application after the change.

If patching must wait, Oracle says blocking attack-required network protocols may reduce risk, but can disrupt functionality. Test any access restriction before production and keep the patch scheduled. Review web tier access logs for unexpected unauthenticated requests and investigate suspicious application tier activity using your normal incident process.

Record patch identifiers and validation results in the patch management process. The November Oracle patch matrix provides context for other product families, while the earlier EBS flaw is a separate October issue. Do not use evidence of that earlier patch as proof that these November fixes are present.

Frequently Asked Questions

Which EBS releases are covered by the two November CVEs?

Oracle lists supported E-Business Suite versions 12.2.3 through 12.2.15 for both CVE-2026-114924 and CVE-2026-114925.

Does EBS 12.2.15 alone prove these flaws are fixed?

No. Oracle identifies affected supported versions through 12.2.15 and directs customers to the November EBS patch availability document for installation-specific patches.

Sources

  1. Oracle, November 2026 Critical Security Patch Update, November 17, 2026
  2. Horizon3, Oracle EBS CVE-2026-114924 and CVE-2026-114925 analysis, November 19, 2026
  3. NIST NVD, CVE-2026-114924
  4. NIST NVD, CVE-2026-114925
  5. CISA, Known Exploited Vulnerabilities Catalog, November 18, 2026
Share this articleLinkedInXEmail
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →