Skip to content
Noroxi
NVD / CVE Program· CNA PSF

CVE-2024-4030: tempfile.mkdtemp() may be readable and writeable by all users on Windows

Noroxi assessment

Priority: Monitor (action score 28/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.30% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Python Software Foundation CPython 3.10.15, 3.11.10, 3.12.4.

Low priority for now. Upgrade to Python Software Foundation CPython 3.10.15, 3.11.10, 3.12.4 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

On Windows a directory returned by tempfile.mkdtemp() would not always have permissions set to restrict reading and writing to the temporary directory by other users, instead usually inheriting the correct permissions from the default location. Alternate configurations or users without a profile directory may not have the intended permissions. If you’re not using Windows or haven’t changed the temporary directory location then you aren’t affected by this vulnerability. On other platforms the returned directory is consistently readable and writable only by the current user. This issue was caused by Python not supporting Unix permissions on Windows. The fix adds support for Unix “700” for the mkdir function on Windows which is used by mkdtemp() to ensure the newly created directory has the proper permissions.

HighCVSS 7.1 · v3.1—No exploit Fix available
Published
May 7, 2024
Updated
Jun 17, 2026
EPSS
0.3% · 22th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-4030

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for python software foundation records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
pythoncpython

Versions reported by the vendor

Affected version ranges reported by the assigning authority (PSF). Independent of NVD's CPE analysis and usually ahead of it.

  • Python Software Foundation CPython

    • before 3.8.20affected · python
    • 3.9.0 and later · before 3.9.20affected · python
    • 3.10.0 and later · before 3.10.15affected · python
    • 3.11.0 and later · before 3.11.10affected · python
    • 3.12.0 and later · before 3.12.4affected · python
    • 3.13.0a1 and later · before 3.13.0b1affected · python

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
openSUSE:Leap 15.6python312before 3.12.4-150600.3.3.13.12.4-150600.3.3.1
openSUSE:Leap 15.6python312-corebefore 3.12.4-150600.3.3.13.12.4-150600.3.3.1
openSUSE:Leap 15.6python312-documentationbefore 3.12.4-150600.3.3.13.12.4-150600.3.3.1
openSUSE:Tumbleweedpython310before 3.10.15-1.13.10.15-1.1
openSUSE:Tumbleweedpython311before 3.11.9-7.13.11.9-7.1
openSUSE:Tumbleweedpython312before 3.12.5-1.13.12.5-1.1
openSUSE:Tumbleweedpython38before 3.8.20-1.13.8.20-1.1
openSUSE:Tumbleweedpython39before 3.9.20-1.13.9.20-1.1
SUSE:Linux Enterprise Module for Python 3 15 SP6python312before 3.12.4-150600.3.3.13.12.4-150600.3.3.1
SUSE:Linux Enterprise Module for Python 3 15 SP6python312-corebefore 3.12.4-150600.3.3.13.12.4-150600.3.3.1
SUSE:Linux Micro 6.0python311before 3.11.11-1.13.11.11-1.1
SUSE:Linux Micro 6.0python311-corebefore 3.11.11-1.13.11.11-1.1
SUSE:Linux Micro 6.1python311before 3.11.12-slfo.1.1_1.13.11.12-slfo.1.1_1.1
SUSE:Linux Micro 6.1python311-corebefore 3.11.12-slfo.1.1_1.13.11.12-slfo.1.1_1.1

Same product

python software foundation: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-115557Distrust compromised intermediate certificates in ssl module
    37Monitor
  • CVE-2025-4517Arbitrary writes via tarfile realpath overflow
    37Monitor
  • CVE-2026-19445Use-after-free of a server-side SSLContext when sni_callback switches contexts
    36Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2023-6597Mar 19, 2024 · An issue was found in the CPython `tempfile.TemporaryDirectory` class affecting versions 3.12.1, 3.11.7, 3.10.13, 3.9.18, and 3.8.18 and pri
    31Monitor
  • ← EarlierCVE-2024-0450Mar 19, 2024 · Quoted zip-bomb protection for zipfile
    24Monitor
  • Later →CVE-2024-4032Jun 17, 2024 · Incorrect IPv4 and IPv6 private ranges
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Python Software Foundation CPython3.10.15Vendor (CNA)
Python Software Foundation CPython3.11.10Vendor (CNA)
Python Software Foundation CPython3.12.4Vendor (CNA)
Python Software Foundation CPython3.13.0b1Vendor (CNA)
Python Software Foundation CPython3.8.20Vendor (CNA)
Python Software Foundation CPython3.9.20Vendor (CNA)
opensuse:python3103.10.15-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:python3113.11.9-7.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:python3123.12.4-150600.3.3.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:python312-core3.12.4-150600.3.3.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:python312-documentation3.12.4-150600.3.3.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:python383.8.20-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:python393.9.20-1.1 · openSUSE:TumbleweedPackage registry (OSV)
suse:python3113.11.11-1.1 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:python311-core3.11.11-1.1 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:python3123.12.4-150600.3.3.1 · SUSE:Linux Enterprise Module for Python 3 15 SP6Package registry (OSV)
suse:python312-core3.12.4-150600.3.3.1 · SUSE:Linux Enterprise Module for Python 3 15 SP6Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
None

Weakness class (CWE)

CWE-276 · Incorrect Default Permissions

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (14 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records