Oracle January 2026 CPU · Released 21 January 2026

Oracle January 2026 CPU — 337 Vulnerabilities Patched

Oracle’s January 2026 Critical Patch Update was the largest single-cycle security release in recent memory — 337 patches across 27 Oracle product families. 47 patches in Oracle Fusion Middleware alone are remotely exploitable without authentication. This was the last quarterly-only CPU before Oracle’s monthly CSPU cadence began.

Released 21 Jan 2026 (3rd Tuesday)
337 security patches
47 unauthenticated RCE in OFM
Jan 2026 CPU Dashboard
LIVE · LAST QUARTERLY-ONLY
Total Patches
337
Product Families
27
OFM Patches
51
Pre-auth RCE (OFM)
47
Top patched families (Jan 2026 CPU)
Oracle Fusion Middleware51
Oracle Communications39
Oracle Financial Services29
Oracle MySQL23
Oracle Database Server12
JANUARY 2026 CPU · KEY NUMBERS

Why the January 2026 CPU Was a Watershed Release

Oracle’s Q1 2026 CPU was the last quarterly-only release before the monthly CSPU cadence began. For US, UK and EU Oracle Fusion teams, it remains the security baseline for the entire 26A window.

337
Security patches
Across all Oracle product families
27
Product families
Database, Fusion, EBS, PeopleSoft, Java SE, MySQL, Siebel + more
51
OFM patches
Oracle Fusion Middleware specifically
47
Pre-auth RCE
Remotely exploitable without credentials

Why January 2026 CPU Still Matters in May 2026

Foundation for 26A & 26B

January 2026 patches are the security baseline assumed by every subsequent Oracle quarterly release. 26A (Feb), 26B (May) and the new monthly CSPUs all build on this foundation.

Compounded by CVE-2026-21992

Environments that haven’t applied the January 2026 OFM patches have compounded exposure to the March 2026 emergency alert (CVE-2026-21992, CVSS 9.8, Oracle IAM RCE).

SOX & Audit Control Trail

For SOX-regulated US filers and FCA/GDPR-regulated UK and EU customers, the January 2026 CPU evidence of patch application is a standard audit control. SyntraFlow tracks this in the audit trail automatically.

JANUARY 2026 CPU · TOP PATCHED FAMILIES

Where the 337 January Patches Landed

Oracle Fusion Middleware accounted for the bulk of high-severity unauthenticated patches, but every Oracle product family received fixes. Each card links to the validation playbook for that area.

CRITICAL
51

Oracle Fusion Middleware

47 remotely exploitable without authentication. Includes WebLogic, OIM/OIG, OWSM, OAM, OHS, BPM, SOA.

HIGH
39

Oracle Communications

Internet-exposed services account for largest attack surface among Communications products.

HIGH
29

Oracle Financial Services Applications

FSGBU, FCCM, Flexcube, OBP and OFSAA security fixes. Material for US/EU banking audit.

MED-HIGH
23

Oracle MySQL

MySQL Server, Connectors, Cluster, Enterprise Backup, Enterprise Monitor patches.

MED-HIGH
15

Oracle Java SE

JDK / JRE security fixes — critical for any Java-based Oracle integration.

MED-HIGH
12

Oracle Database Server

Server, Net Services, Workspace Manager, Application Express, Spatial & Graph.

MEDIUM
11

Oracle E-Business Suite

12.2 and 12.1 EBS application server modules — HRMS, AR, AP, GL, PO.

MEDIUM
9

Oracle PeopleSoft

HCM, Financials, ELM, CRM and PeopleTools security fixes. Pre-auth RCE in select modules.

MEDIUM
8

Oracle JD Edwards

EnterpriseOne Tools and applications — affecting manufacturing and distribution customers.

MEDIUM
7

Oracle Siebel CRM

Siebel Core, Mobile and Industry applications across CRM verticals.

MEDIUM
7

Oracle Retail Applications

RMS, ReSA, RPM and other Retail Suite patches.

MEDIUM
6

Oracle GoldenGate

Replication and Big Data adapter security patches.

VALIDATION PRIORITIES

Three-Tier Patching & Testing Plan

If your Oracle environment still hasn’t fully applied January 2026 CPU patches (most environments haven’t — over half of large Oracle deployments lag the CPU by 60+ days), use this priority order.

TIER 1 · PATCH WITHIN 72 HOURS

Oracle Identity Manager, OWSM & WebLogic

Combined with the March 2026 out-of-band alert, these patches are your absolute highest priority. Any CVE in OIM, OWSM or WebLogic with CVSS > 9.0 should be treated as a P1 incident. Affects nearly every US, UK and EU enterprise Oracle deployment.

  • • Oracle Identity Manager (OIM/OIG) — patch + validate SCIM and REST endpoints
  • • Oracle Web Services Manager (OWSM) — included in many Fusion Middleware deployments
  • • Oracle WebLogic Server — 14c and 12.2.x
TIER 2 · PATCH WITHIN 2 WEEKS

Internet-Facing Fusion Middleware & Communications

Any Oracle service exposed to the public internet. Higher impact for organisations with hybrid (Customer-managed + Oracle-managed) deployments.

  • • Oracle HTTP Server (OHS) — frontline web tier
  • • Oracle REST Data Services (ORDS) — if exposed
  • • Oracle Communications products with internet endpoints
  • • Oracle Access Manager (OAM) — SSO front-door
TIER 3 · NEXT MAINTENANCE WINDOW

Database, MySQL, Java SE, EBS, PeopleSoft, JDE

Internal-only systems. Schedule into your normal change window but don’t defer past the next quarterly maintenance.

RELEASE INTELLIGENCE

How SyntraFlow Validates the Jan 2026 CPU

Instead of running a full regression suite, SyntraFlow Release Intelligence maps each January 2026 advisory against your tenant configuration and produces a targeted test plan covering only the components actually affected.

STEP 1

Tenant Inventory · Fusion Middleware Components

Identifies every OIM, OWSM, OAM, OHS, WebLogic, BPM, SOA Suite deployment in your tenant — including bundled installs you may not realise exist.

STEP 2

CVE ↔ Component Mapping

Each of the 337 January CPU advisories is matched to the specific components actually deployed in your tenant — typically reducing scope to 30–60 advisories that actually apply.

STEP 3

Regression Test Pack Auto-Composition

For each in-scope advisory, SyntraFlow auto-composes the regression test path — SSO + SCIM + role-based access + identity-aware integration payloads + REST API contracts.

STEP 4

SOX / GDPR Audit Evidence

Every test result is timestamped and stored as audit evidence for SOX (US), FCA/PRA (UK), GDPR (EU), and ISO 27001 controls covering patch management.

January 2026 CPU FAQ

What is the Oracle January 2026 CPU?

The Oracle January 2026 Critical Patch Update is Oracle’s first quarterly security release of 2026 — 337 patches across 27 product families. It was the largest single-cycle Oracle security release in recent memory and remains the security baseline for the 26A release window.

How many vulnerabilities did it fix?

337 distinct patches. 51 patches were for Oracle Fusion Middleware specifically, and 47 of those were remotely exploitable without authentication — meaning a network-based attacker can exploit them with no credentials.

Why does the January CPU still matter in May 2026?

Because most large Oracle environments take 60+ days to fully roll out a quarterly CPU. Many US, UK and EU enterprises still hadn’t completed January 2026 patching when the March 2026 emergency alert dropped — compounding their exposure to CVE-2026-21992.

How is January 2026 CPU different from May 2026 CSPU?

January 2026 was the last quarterly-only Oracle CPU. From May 28, 2026 onwards, Oracle ships a monthly CSPU on top of the existing quarterly CPU. January 2026 represents the legacy model — large, infrequent, and comprehensive.

What does SyntraFlow do for January CPU validation?

SyntraFlow Release Intelligence maps every January 2026 advisory against your Oracle Fusion tenant’s actual configuration — typically narrowing 337 patches down to the 30–60 that actually apply to you. Then auto-composes a regression test pack only for those, with SOX / GDPR audit evidence.

Get a tenant-specific January 2026 CPU exposure report

SyntraFlow scans your Oracle Fusion tenant, identifies which of the 337 January 2026 CPU advisories actually apply, and auto-composes a regression test pack with full audit trail. Used by US, UK and EU enterprise Oracle teams.