Oracle has released Oracle Key Vault 21.16 and urges all customers to apply it right away. Oracle announced the update on its Database blog on November 12, 2026. It is a security-focused release that covers the server appliance as well as the endpoint client software.
Key Vault holds the encryption keys, wallets and secrets for many databases and applications. A weakness there can reach a large number of systems, which is why Oracle treats this patch as urgent.
What the Update Contains
The update carries security fixes for the parts that make up the appliance. The embedded Oracle Database moves to the October 2026 Release Update 19.33, and the fixed flaws are listed in the October 2026 Critical Patch Update.
- Integrated components: stability and security updates for the bundled APEX, ORDS and GoldenGate.
- Java: Java SE fixes, among them CVE-2026-91403 and CVE-2026-114820, which Oracle links to eMudhra certificate trust problems.
- Operating system: security updates for the embedded Oracle Linux 8.10.
- General: reliability and operational improvements across the platform.
Oracle says anyone on 21.15, even with monthly patches applied, or on an earlier supported release should move to 21.16.
Upgrading Without Downtime
Key Vault uses a multi-master cluster, so nodes can be upgraded one at a time while the others keep serving clients, including Oracle databases. Oracle notes this keeps databases and applications available when the cluster is set up properly.
The 21.16 server still works with older supported endpoints. You do not need to upgrade every endpoint on the same day, although Oracle strongly recommends doing so soon.
For Oracle AI Database 26ai, Oracle describes endpoint upgrades with almost no downtime, built on PKCS#11 libraries tied to the release. After you complete the required configuration once, later endpoint upgrades need no database outage. Older database versions should follow the procedures for their own setup, using rolling upgrades where they apply.
Monthly Recommended Patches
Since Key Vault 21.15, Oracle publishes release-specific Monthly Recommended Patches when needed between Release Updates. They can include fixes for the embedded database, Oracle Linux and other components.
Oracle confirms you can go straight from 21.15 to 21.16 with the normal upgrade procedure, even if those patches are installed. You do not have to roll them back or remove them first.
What It Means for Security Teams
Oracle's message is about speed. It argues that attackers using automated tools find and exploit flaws faster, so the time between a disclosure and a patch matters more than before. A secrets store is a high-value target, so it should be near the top of the patch queue.
Plan the rollout in the order Oracle suggests: read the release notes, check the upgrade paths in the installation and upgrade guide, then patch one cluster node at a time. Test an endpoint upgrade on a non-production database before the rest. Related background is in our report on the new monthly Exadata software release schedule.
Where to Get It
- Existing deployments: download patch 40263130.
- New installations: Oracle Software Delivery Cloud.
- Oracle Cloud Infrastructure: Oracle Cloud Marketplace.
- Other clouds and appliances: Azure, AWS and Google Cloud installs, and Oracle Database Appliance.
Conclusion
Oracle Key Vault 21.16 bundles database, Java, Linux and component fixes in one update that can be applied with rolling upgrades. If you run Key Vault, schedule it now and plan the endpoint upgrades after it.
Sources
See my articles more often when you search Google.
