CVE-2025-11919: Unprotected temporary directories in Wolfram Cloud may result in privilege escalation
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.
Security readout for executives and security teams
Plain-English summary
CVE-2025-11919 is a critical privilege-escalation issue in Wolfram Cloud 14.2. A user with access to shared temporary storage may influence another user’s JVM startup so attacker-controlled code is loaded. This can compromise confidentiality and integrity across user boundaries on the same cloud instance.
Executive priority
Treat as urgent for any multi-user Wolfram Cloud 14.2 environment. The business risk is cross-user code execution and data exposure within shared cloud instances. Prioritize confirmation of exposure and vendor-supported remediation before expanding shared workloads.
Technical view
The default JVM can access files under /tmp, including /tmp/UserTemporaryFiles for other users. During JVM startup, an -init file exists in this vulnerable directory. An attacker with shared /tmp access can pre-position or replace classpath-resolved .jar files or directories so the victim JVM loads attacker-controlled classes first.
Likely exposure
Exposure is likely limited to Wolfram Cloud 14.2 environments where multiple users share a cloud instance and temporary directory space. The issue requires attacker access to the shared /tmp area, but no victim interaction is required according to the CVSS vector.
Exploitation context
The CVE is not listed as KEV in the provided data, and the sources do not state active exploitation. The published scenario describes low-complexity exploitation by an authenticated or otherwise present user with access to shared temporary storage on the same instance.
Researcher notes
The root issue is unprotected temporary directory access combined with JVM classpath resolution during startup. The record maps to CWE-552 and CVSS 9.6, with scope changed and high confidentiality/integrity impact. Public sources identify Wolfram Cloud 14.2 only; no broader affected-version claims should be made.
Mitigation direction
Review Wolfram and CERT guidance for an official fix or workaround.
Isolate per-user temporary directories where administratively possible.
Restrict cross-user access to shared temporary storage.
Avoid multi-user sharing on vulnerable Wolfram Cloud 14.2 instances until addressed.
Monitor for unexpected files or libraries in shared temporary paths.
Validation and detection
Identify Wolfram Cloud deployments running version 14.2.
Determine whether users share /tmp or /tmp/UserTemporaryFiles on the same instance.
Review JVM startup behavior for classpath entries sourced from temporary directories.
Check vendor advisories for patched versions or configuration changes.
Assess logs and filesystem telemetry for suspicious temporary JAR placement.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-552: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
2ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-552 · source CWE mapping
Files or Directories Accessible to External Parties
Files or Directories Accessible to External Parties represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.