Oracle Platform Security for Java CVE-2026-114824: CVSS 10.0, patch now

A critical flaw in Oracle Platform Security for Java needs no login and scores 10.0. See affected versions, how to check and how to mitigate it.

CVE-2026-114824: CVSS 10.0, no login needed: patch

TL;DR

  • CVE-2026-114824 is a critical flaw in Oracle Platform Security for Java, part of Oracle Fusion Middleware, published on November 17, 2026.
  • Oracle scored it with a CVSS v3.1 base score of 10.0. An unauthenticated attacker with network access over HTTP can take over the product, and the damage can spread to other products.
  • The affected supported versions named in the record are 12.2.1.4.0 plus 14.1.2.0.0.
  • The records do not say it is exploited in the wild, but it needs no login, so treat it as urgent.
  • No fixed version appears in the record: apply the patch listed in Oracle's own advisory and keep the service off untrusted networks until you do.

What the flaw is, in plain English

Oracle Platform Security for Java is the security layer that many Oracle Fusion Middleware applications rely on for things such as authentication and authorisation. When it breaks, every application that trusts it is affected. The flaw sits in a component that bundles third party jars, which are the Java libraries shipped inside the product.

According to the NVD entry for CVE-2026-114824, the weakness is easy to exploit. An attacker does not need an account. They only need to reach the service over the network with HTTP requests. A successful attack can end in a takeover of Oracle Platform Security for Java itself.

The record also points out a scope change. In plain words, the attacker starts at one component but the damage is not limited to it: other products that depend on it can be affected too. That is why the score is the maximum. A takeover of the security layer is not a problem of one application only, because the applications behind it assume that layer is honest.

Why it matters now

Several things make this worth acting on quickly rather than at the next maintenance window.

  • Severity. Oracle assigned a CVSS v3.1 base score of 10.0. The score describes an attack from the network, with low complexity, no privileges and no user interaction, with high impact on confidentiality, integrity and availability.
  • It is new. The entry was published on November 17, 2026 and is still waiting for NVD analysis. Early in the life of an advisory, defenders are racing with people who read the same text and try to turn it into an attack.
  • It protects other things. A middleware security layer is rarely alone. Web portals, internal tools and integrations often sit behind it, so one flaw can open several doors.
  • It is easy to miss. Middleware installs tend to be set up once and left alone, and they may sit on servers owned by a team that does not track Java runtimes.

If you are already planning other work on Java this week, fold this in. Our weekly patch roundup shows how we triage a long list, and our guide to patching Ubuntu servers without surprise reboots covers the operating system side of the same maintenance window.

Am I affected?

The record names two supported versions of Oracle Platform Security for Java: 12.2.1.4.0 plus 14.1.2.0.0. If you run Oracle Fusion Middleware on either of those, treat the server as affected until Oracle's advisory tells you which patch level is safe. If you run another version, do not assume you are clear: the record lists only the supported versions that Oracle named, so confirm against Oracle's advisory.

The flaw needs network access to the service, so the first question is where the service can be reached from. A server that is open to the internet is more exposed than one on a private network, but an attacker who is already inside your network, or a compromised workstation, is exactly who a flaw like this helps. Do not treat internal as safe.

To check one machine by hand, find out whether Java and a Fusion Middleware home are installed, and which versions:

java -version
ps aux | grep -i weblogic

Fusion Middleware keeps its patch inventory in its own tooling. Run the inventory command that Oracle documents for your install, from the Oracle home directory, and compare the listed patches with the advisory. We deliberately do not list a command that we cannot check against the records: use Oracle's documentation for that step. On a package based server, also ask the package manager what is installed:

dpkg -l | grep -i java
rpm -qa | grep -i java

The distribution backport caveat applies to Java packages that come from your Linux distribution: the version string may not change when the vendor backports a fix. Oracle Fusion Middleware itself is not a distribution package, so for that product the patch level in Oracle's inventory is what counts.

How to mitigate CVE-2026-114824

  1. List every Oracle Fusion Middleware installation you own, across servers, virtual machines and container images. Write down the Oracle Platform Security for Java version of each, and whether it is 12.2.1.4.0 or 14.1.2.0.0.
  2. Open Oracle's advisory for this CVE, which the NVD entry links, and find the patch for your release. The record we used does not give a fixed version, so do not guess one: take it from Oracle.
  3. Restrict network access to the affected service until you can patch. Allow only the clients and gateways that need it. This reduces exposure but does not fix the flaw, so treat it as a stopgap.
  4. Apply Oracle's patch in a test environment first, then in production, following Oracle's instructions for the patch tool and for restarting the managed servers.
  5. Check the installed patch level again after the restart and confirm it matches the advisory. Then review your access logs for unusual HTTP requests to the service from before the patch, and rotate any credentials stored by that layer if you find anything you cannot explain.

The advisory does not describe a configuration setting that switches the behaviour off, so we do not suggest one. Patching is the fix.

How to check with Stackurity

Doing the inventory by hand works for one server. It does not work when Java runtimes and middleware are spread across servers and images owned by different teams.

Stackurity keeps one live inventory of the software on your servers, deployed applications, repositories and container images, and matches it against new vulnerability advisories every hour. Its read-only agent finds Java software on Linux servers and, when you opt in with the --docker flag, in the images of running containers. When an advisory matches, the finding names the component, where it is installed and the version to move to, and one fix groups every place that needs the same upgrade. The remediation documentation explains how fixes are ordered, most urgent first.

After you patch, Check again asks the agent for a fresh report and records whether the issue is really gone, so you do not have to take a ticket status on trust. There are limits: Stackurity does not cover appliance firmware or libraries copied into an application outside a package manager, and runtimes installed by hand are checked for end of life only. A Fusion Middleware home that was unpacked by hand may therefore need a manual check against Oracle's advisory.

Start a free trial of Stackurity to see which of your servers and images run Java today.

FAQ

What is CVE-2026-114824?

It is a critical flaw in Oracle Platform Security for Java, a component of Oracle Fusion Middleware. NVD records that an unauthenticated attacker with network access over HTTP can take over the product, and that the impact can reach other products.

Which versions are affected?

The record names the supported versions 12.2.1.4.0 plus 14.1.2.0.0. It does not list other branches, so check Oracle's advisory for the exact patch that applies to yours.

Is there a fixed version?

The record we used does not give a fixed version. Oracle publishes the patches in its own advisory, so read it and apply the patch for your release instead of guessing a version number.

How severe is CVE-2026-114824?

Oracle scored it with a CVSS v3.1 base score of 10.0, the highest possible. The score reflects an attack over the network that needs no login and no user action.

Is CVE-2026-114824 exploited in the wild?

The records we checked do not say it is exploited, and it is not an entry we know of in the CISA catalogue. Because it needs no login and was only published recently, treat it as urgent anyway.

Does Stackurity find Oracle Platform Security for Java?

Stackurity finds Java software on Linux servers and in images and matches it against advisories, but it does not cover appliance firmware or libraries copied into an application outside a package manager. A Fusion Middleware install that sits in a vendor directory may need a manual check.

Sources: NIST National Vulnerability Database, CVE-2026-114824.