English version
Oracle's October 2026 Critical Patch Update lists CVE-2026-101521 in Oracle APEX with a CVSS 3.1 score of 9.8. Oracle describes it as remotely exploitable over HTTPS without authentication. Successful exploitation may result in an Oracle APEX takeover.
Which APEX releases are listed as affected?
Oracle lists these supported release ranges in its risk matrix:
- APEX 24.1.0 through 24.1.21
- APEX 24.2.0 through 24.2.20
- APEX 26.1.0 through 26.1.4
These ranges are the versions named in the advisory. If your deployment is on an older or unsupported release, do not assume it is unaffected; check Oracle's support and patch guidance for that installation.
A measured response
Start by building an inventory of APEX installations and their release numbers. Prioritize instances reachable from untrusted networks, then review Oracle's Critical Patch Update and the patch availability instructions for the exact release and platform.
Plan the update in a test environment first. Check application sign-in, core workflows, integrations, and deployment procedures. Once validation is complete, schedule the production change, take the backups required by your recovery plan, and record the installed patch level.
Afterward, verify the running release and repeat the checks that matter to your applications. Keep the advisory and patch record with the change so the team can show which systems were assessed and when.
Check the full October CPU
The APEX risk matrix also includes another APEX issue, CVE-2026-66010, with different affected release ranges and a different CVSS score. Review the complete advisory instead of assuming the critical CVE is the only relevant item in the quarterly update.
Use Oracle's October 2026 Critical Patch Update and its text risk matrices as the source of truth for affected versions and patch guidance.