CVE-2025-11919
Unprotected temporary directories in Wolfram Cloud may result in privilege escalation
Description
The default JVM can access files and directories under `/tmp/` including the `$TemporaryDirectory` of other users on the same cloud instance (`/tmp/UserTemporaryFiles/`). The `-init` file for the the JVM initialization exists in the vulnerable directory during the startup of the JVM. An attacker with access to the shared `/tmp/` space can preemptively create or replace `.jar` files or directories (via the `-init` file) that the victim JVM will resolve first in its classpath. By strategically placing a malicious version of a commonly used library (e.g., `commons-io`) in a location that is included in the classpath before the legitimate version, an attacker can cause the JVM to load the malicious class during startup, thereby executing the attacker's code.
INFO
Published Date :
June 26, 2026, 3:39 p.m.
Last Modified :
June 26, 2026, 3:49 p.m.
Remotely Exploit :
No
Source :
certcc
Affected Products
The following products are affected by CVE-2025-11919
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Restrict write access to the /tmp/ directory.
- Configure JVM to prioritize trusted JAR locations.
- Review and remove suspicious files in /tmp/.
- Apply security patches for JVM.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2025-11919 vulnerability anywhere in the article.