cve.bz

CVE-2026-97209 Insecure temporary file in mix deps.partition lets a local user execute code in another user's dependency build

5.4 mediumEPSS 0.2%

Medium (5.4) in elixir-lang elixir. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
Insecure Temporary File vulnerability in Mix deps.partition in Elixir allows a local user to execute code as another user via a swapped partition config file. Partitioned dependency compilation passes the project configuration to each partition VM through a file in a fixed-name directory under the shared system temporary directory, and the partition trusts what it reads back. Another local user on the same host can exploit this during a mix deps.compile run that uses partitioned compilation. Mix.Tasks.Deps.Partition.server/4 in lib/mix/lib/mix/tasks/deps.partition.ex creates the directory with File.mkdir_p/1, which accepts an existing directory without checking its owner, so a user who created it first can replace the file before client/0 reads it. This issue affects mix: from 1.20.0-rc.4 before 1.20.5.

Severity

CVSS 4.0

5.4 medium
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
EPSS
0.2% (unchanged from 0.1% a week ago) estimated probability of exploitation activity in the next 30 days; 12th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2026-10-30. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-379 Creation of Temporary File in Directory with Insecure Permissions
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
EEF (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-97209 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-97209?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-97209?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-97209 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
elixir-lang elixirfrom 1.20.0-rc.4 before 1.20.5

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14elixir-lang1.20.5+dfsg-1DEBIAN-CVE-2026-97209
Ubuntu14.04:LTS, 16.04:LTS, 18.04:LTSelixirno fix listedUBUNTU-CVE-2026-97209

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as Moderate severity because exploitation requires local access on a shared multi-user system and depends on an optional, non-default feature. The attack specifically targets concurrent dependency compilation workloads that have been explicitly configured with partitioned compilation. Furthermore, exploitation hinges on a timing window where an unprivileged local user must pre-create or replace configuration files within a shared directory before worker processes consume them.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-97209.

References

Check your stackJSON