What changed
One release, many product-specific decisions
Oracle's November 2026 Critical Security Patch Update contains 655 new security patches across its product portfolio. That is a count of patches, not a claim of 655 distinct CVEs. The advisory includes product-specific tables for areas such as Database Server, E-Business Suite and Fusion Middleware, with affected versions and component details. A single organization may need several different update paths.
The update also includes the Java SE fix for CVE-2026-114938, the Base64 decoder issue being discussed as Java4Shell. That issue deserves its own runtime and processor check. It should not be used as shorthand for every Oracle product listed in the wider update.
Read the row for your product
Defender workflow
Turn the advisory into a worklist
- 1
Map the Oracle estate. List deployed Oracle products, versions, exposed services, owners and maintenance windows. Include components bundled with business applications and Java runtimes inside images or appliances.
- 2
Prioritize the reachable paths. Use Oracle's affected-version and component tables to identify applicable patches. Give early attention to externally reachable services and systems with sensitive business or identity roles.
- 3
Verify the running version. Follow product-specific update instructions, confirm services restarted where required, and record the active build after change. Keep exceptions and compensating controls tied to a named product and owner.
Defender note
Do not stop at the host package list
Java and Oracle middleware are often packaged inside an application or container. The system package manager may look current while a service runs an older embedded component. Compare the actual process and image inventory with the advisory, especially for products whose updates are delivered on a separate vendor schedule.