On this page (6 sections)
CVE-2026-114824 is a critical vulnerability in Oracle Platform Security for Java, a product within Oracle Fusion Middleware. The affected component is called Centralized Thirdparty Jars. According to the record, an attacker who needs no login and can reach the service over HTTP may compromise the product, and the issue carries the maximum CVSS 3.1 base score of 10.0. The National Vulnerability Database lists it as published on November 17, 2026.
If you run Oracle Fusion Middleware 12.2.1.4.0 or 14.1.2.0.0, investigate this today. The public record is thin, so this article keeps what is stated apart from what is still unknown.
What the record says
The description is brief. It calls the flaw easily exploitable and says an unauthenticated attacker with network access via HTTP can compromise Oracle Platform Security for Java, with takeover of that product as the stated outcome. It also notes a scope change: the weakness is in Oracle Platform Security for Java, but attacks may significantly impact additional products.
The linked Oracle security alert is the vendor reference for this CVE. Its text was not part of the research for this article, so patch details, fixed versions and the list of impacted products are not covered here. Read the alert directly before planning your update.
Reading the CVSS vector in plain terms
| Metric | Value | Practical meaning |
|---|---|---|
| Attack vector | Network | Reachable remotely, no local access needed |
| Attack complexity | Low | No special conditions have to line up |
| Privileges required | None | No account or login needed |
| User interaction | None | No one has to click anything |
| Scope | Changed | Impact can reach beyond the vulnerable component into other products |
| Confidentiality, integrity, availability | High, High, High | Full loss of all three if exploited |
Together these values produce the maximum score. The scope change matters most for planning: the record says other products may be affected, so the damage may extend past the single product named. Oracle's alert is the place to confirm which ones.
What is not known yet
- The weakness type: the GitHub entry lists no CWE.
- Fixed or patched versions: the GitHub advisory shows both as unknown and lists no package.
- Whether anyone is exploiting it: no source reports exploitation, and the research found no CISA KEV listing.
- Root cause or proof-of-concept details: none appear in the sources, and this article does not speculate.
Who is realistically exposed
Exposure depends on whether the vulnerable component can be reached over HTTP. Internet-facing Fusion Middleware instances, and admin or application endpoints published through a reverse proxy, carry the most risk. Internal-only deployments are not safe by default either: anyone who gains a foothold on the network could try the same route, given the unauthenticated, low-complexity profile. Because of the scope change, also ask which of your applications depend on Oracle Platform Security for Java, and check Oracle's alert for the products it says are impacted.
What to do now
Start with an inventory, then follow Oracle's guidance for the fix. The command below is a read-only check and should be adapted to your environment.
- List every Oracle Fusion Middleware installation and note its version; flag 12.2.1.4.0 and 14.1.2.0.0.
- Open the Oracle security alert for this CVE and identify the patch or fixed release for your version.
- Schedule the patch with priority; if you cannot patch immediately, restrict network access to the affected services to trusted hosts only.
- Remove any direct internet exposure of Fusion Middleware HTTP endpoints that is not needed, or put them behind a reverse proxy or firewall with tight rules.
- Review web server and access logs for unusual unauthenticated requests to Fusion Middleware endpoints since at least November 17, 2026.
- After patching, confirm the new version and restart services in a maintenance window.
This command lists the patches recorded in an Oracle home using Oracle's OPatch tool. Run it as the Oracle software owner from the OPatch directory of the affected home, and compare the output with the patch named in Oracle's alert:
./opatch lsinventoryDetection and monitoring
No indicators of compromise have been published, so detection has to be general. Watch for unexpected HTTP requests from unfamiliar addresses to Fusion Middleware ports, new or modified files in the Oracle home and domain directories, unexpected child processes of the Java servers, and new outbound connections from application servers. Ship logs off the host if possible so they survive a compromise.
From the outside, you can watch the certificates, DNS and headers of public-facing hosts with Webforta Monitor, which helps you notice unplanned changes on exposed systems. It will not tell you whether this specific flaw is present. If you suspect a host is already compromised, follow the steps in Website hacked: what to do. For broader habits that reduce exposure, see Small business website security.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
