Skip to content

chore(deps): Update dependency setuptools to v83 [SECURITY] - autoclosed - #1562

Closed
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/pypi-setuptools-vulnerability
Closed

renovate[bot] wants to merge 1 commit into
masterfrom
renovate/pypi-setuptools-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Sep 26, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
setuptools (changelog) >=77.0.1 → >=83.0.0 age confidence

setuptools has a path traversal vulnerability in PackageIndex.download that leads to Arbitrary File Write

BIT-setuptools-2025-47273 / CVE-2025-47273 / GHSA-5rjg-fvgr-3xxf / PYSEC-2025-49

More information

Details

Summary

A path traversal vulnerability in PackageIndex was fixed in setuptools version 78.1.1

Details
    def _download_url(self, url, tmpdir):
        # Determine download filename
        #
        name, _fragment = egg_info_for_url(url)
        if name:
            while '..' in name:
                name = name.replace('..', '.').replace('\\', '_')
        else:
            name = "__downloaded__"  # default if URL has no path contents

        if name.endswith('.[egg.zip](http://egg.zip/)'):
            name = name[:-4]  # strip the extra .zip before download

 -->       filename = os.path.join(tmpdir, name)

Here: https://github.com/pypa/setuptools/blob/6ead555c5fb29bc57fe6105b1bffc163f56fd558/setuptools/package_index.py#L810C1-L825C88

os.path.join() discards the first argument tmpdir if the second begins with a slash or drive letter.
name is derived from a URL without sufficient sanitization. While there is some attempt to sanitize by replacing instances of '..' with '.', it is insufficient.

Risk Assessment

As easy_install and package_index are deprecated, the exploitation surface is reduced.
However, it seems this could be exploited in a similar fashion like GHSA-r9hx-vwmv-q579, and as described by POC 4 in GHSA-cx63-2mw6-8hw5 report: via malicious URLs present on the pages of a package index.

Impact

An attacker would be allowed to write files to arbitrary locations on the filesystem with the permissions of the process running the Python code, which could escalate to RCE depending on the context.

References

https://huntr.com/bounties/d6362117-ad57-4e83-951f-b8141c6e7ca5
https://github.com/pypa/setuptools/issues/4946

Severity

  • CVSS Score: 7.7 / 10 (High)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


BIT-setuptools-2025-47273 / CVE-2025-47273 / GHSA-5rjg-fvgr-3xxf / PYSEC-2025-49

More information

Details

setuptools is a package that allows users to download, build, install, upgrade, and uninstall Python packages. A path traversal vulnerability in PackageIndex is present in setuptools prior to version 78.1.1. An attacker would be allowed to write files to arbitrary locations on the filesystem with the permissions of the process running the Python code, which could escalate to remote code execution depending on the context. Version 78.1.1 fixes the issue.

Severity

  • CVSS Score: 8.8 / 10 (High)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

References

This data is provided by OSV and the PyPI Advisory Database (CC-BY 4.0).


setuptools: MANIFEST.in exclusion bypass in sdist via Unicode normalization collision (NFC/NFD) on macOS APFS/HFS+

BIT-setuptools-2026-59890 / CVE-2026-59890 / GHSA-h35f-9h28-mq5c / PYSEC-2026-3447

More information

Details

Summary

When building a source distribution (python -m build --sdist / setup.py sdist), setuptools' FileList applies MANIFEST.in directives (exclude, global-exclude, recursive-exclude, prune) by matching a compiled glob against on-disk file names byte-for-byte, with no Unicode normalization. On normalization-preserving filesystems (notably macOS APFS and HFS+), a file written in NFD and a MANIFEST.in rule written in NFC refer to the same file but are byte-distinct, so the exclusion silently fails to match. A file the maintainer intended to exclude is then packed into the .tar.gz and, if published, uploaded to the public, immutable PyPI index.

Details

File names in FileList.files come from os.walk (setuptools/_distutils/filelist.py, _find_all_simple), so on APFS a file written NFD is offered to the matcher in NFD, while the MANIFEST.in pattern carries the author's editor form (typically NFC). The matching path performs no canonicalization:

##### setuptools/command/egg_info.py  (FileList.global_exclude)
def global_exclude(self, pattern):
    match = translate_pattern(os.path.join('**', pattern))   # fnmatch.translate -> regex, no NFC/NFD
    return self._remove_files(match.match)                   # byte-level regex over raw os.walk names

A rule written NFC (café = 63 61 66 c3 a9) does not match an on-disk name written NFD (café = 63 61 66 65 cc 81), even though the filesystem treats the two as one file.

A unicodedata.normalize('NFD', ...) helper exists in setuptools/unicode_utils.py (decompose()), but it is never called in the manifest matching path, so neither the pattern nor the walked path is normalized before matching. The only normalization in this area, EggInfoCommand._manifest_normalize, uses filesys_decode (bytes→str decode only, no NFC/NFD) and runs when writing SOURCES.txt, after matching has already occurred.

Impact

MANIFEST.in exclusions are the documented mechanism maintainers use to keep secrets, local configs, and private fixtures out of the published sdist. A non-ASCII excluded file may be published to the public, immutable PyPI index despite the rule — an irreversible disclosure with no visual cue (NFC and NFD forms render identically). Exposure is filesystem-dependent and most relevant on macOS APFS/HFS+, where many maintainers build and publish. Pure-ASCII rules are unaffected.

Proof of concept

With a project containing MANIFEST.in:

global-include *.txt *.json
global-exclude secret_café.txt    # rule saved NFC

and an on-disk file secret_café.txt written in NFD, python -m build --sdist packs the secret file into the resulting .tar.gz, while an ASCII control file excluded by the same directive is correctly dropped — isolating the bypass to the NFC-pattern vs. NFD-name mismatch. Reproduced on macOS APFS with setuptools 82.0.1.

Remediation

Normalize both the walked path and each MANIFEST.in pattern to a single canonical form before matching, in both setuptools/command/egg_info.py (FileList) and the vendored setuptools/_distutils/filelist.py. For an exclusion list, err toward excluding more, and document that MANIFEST.in matching is normalization-insensitive on macOS.

Credit

Reported by Tomas Illuminati. Coordinated via CERT/CC VINCE VU#604762.

Severity

  • CVSS Score: 6.1 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


BIT-setuptools-2026-59890 / CVE-2026-59890 / GHSA-h35f-9h28-mq5c / PYSEC-2026-3447

More information

Details

setuptools is a package that allows users to download, build, install, upgrade, and uninstall Python packages. Prior to 83.0.0, FileList applied MANIFEST.in exclude, global-exclude, recursive-exclude, and prune directives by matching compiled glob patterns against on-disk file names without Unicode normalization, so on macOS APFS or HFS+ an NFD file name could bypass an NFC exclusion rule and be packed into a source distribution. This issue is fixed in version 83.0.0.

Severity

  • CVSS Score: 6.1 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N

References

This data is provided by OSV and the PyPI Advisory Database (CC-BY 4.0).


Release Notes

pypa/setuptools (setuptools)

v83.0.0

Compare Source

v82.0.1

Compare Source

v82.0.0

Compare Source

v81.0.0

Compare Source

v80.10.2

Compare Source

v80.10.1

Compare Source

v80.9.0

Compare Source

v80.8.0

Compare Source

v80.7.1

Compare Source

v80.7.0

Compare Source

v80.6.0

Compare Source

v80.4.0

Compare Source

v80.3.1

Compare Source

v80.3.0

Compare Source

v80.2.0

Compare Source

v80.1.0

Compare Source

v80.0.1

Compare Source

v80.0.0

Compare Source

v79.0.1

Compare Source

v79.0.0

Compare Source

v78.1.1

Compare Source

v78.1.0

Compare Source

v78.0.2

Compare Source

v78.0.1

Compare Source

v77.0.3

Compare Source


Configuration

📅 Schedule: (in timezone Europe/Vienna)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot requested a review from lusoris as a code owner September 26, 2026 18:27
@github-actions github-actions Bot added the type:chore Maintenance, no user-visible change label Sep 26, 2026
@renovate
renovate Bot force-pushed the renovate/pypi-setuptools-vulnerability branch from 85b2dcf to b8b879f Compare September 26, 2026 18:29
@renovate renovate Bot changed the title chore(deps): Update dependency setuptools to >=77.0.3 [SECURITY] chore(deps): Update dependency setuptools to v83 [SECURITY] Sep 26, 2026
@renovate
renovate Bot force-pushed the renovate/pypi-setuptools-vulnerability branch from b8b879f to bced1f7 Compare September 26, 2026 19:14
@renovate renovate Bot changed the title chore(deps): Update dependency setuptools to v83 [SECURITY] chore(deps): Update dependency setuptools to >=77.0.3 [SECURITY] Sep 26, 2026
@renovate
renovate Bot force-pushed the renovate/pypi-setuptools-vulnerability branch from bced1f7 to 44be814 Compare September 26, 2026 19:21
@renovate renovate Bot changed the title chore(deps): Update dependency setuptools to >=77.0.3 [SECURITY] chore(deps): Update dependency setuptools to v83 [SECURITY] Sep 26, 2026
@renovate
renovate Bot force-pushed the renovate/pypi-setuptools-vulnerability branch from 44be814 to 9ae4d3e Compare September 26, 2026 20:05
@renovate renovate Bot changed the title chore(deps): Update dependency setuptools to v83 [SECURITY] chore(deps): Update dependency setuptools to >=77.0.3 [SECURITY] Sep 26, 2026
@renovate
renovate Bot force-pushed the renovate/pypi-setuptools-vulnerability branch from 9ae4d3e to 1e91397 Compare September 26, 2026 20:07
@renovate renovate Bot changed the title chore(deps): Update dependency setuptools to >=77.0.3 [SECURITY] chore(deps): Update dependency setuptools to v83 [SECURITY] Sep 26, 2026
@lusoris

lusoris commented Sep 26, 2026

Copy link
Copy Markdown
Contributor

Superseded by #1566 (d345c12): master's docs/requirements.txt and python/pyproject.toml already require setuptools>=83.0.0 and wheel>=0.46.2, with the hash locks restamped.

@lusoris lusoris closed this Sep 26, 2026
@renovate renovate Bot changed the title chore(deps): Update dependency setuptools to v83 [SECURITY] chore(deps): Update dependency setuptools to v83 [SECURITY] - autoclosed Sep 26, 2026
@renovate
renovate Bot deleted the renovate/pypi-setuptools-vulnerability branch September 26, 2026 21:44
lusoris pushed a commit that referenced this pull request Oct 5, 2026
… defects on the known-upstream page

The known-upstream page listed #1562 only. It now has a dated section for
the GPU reports checked on 2026-10-05:

- #1566 (fixed upstream by #1552): the CUDA motion kernel above 8 bits
  advanced a 16-bit pointer by the byte stride. Not affected: the fork's
  SAD kernel reads a row through a byte pointer (load_sample()), equal to
  the CPU in test_cuda_exact_twins, test_cuda_motion_tiny_frames and the
  depth and layout matrix; the planted upstream form fails above 8 bits and
  gives 26993 invalid reads under compute-sanitizer memcheck.
- #1564 bugs 1 to 3 (CUDA masking border rows, per-warp rounding, x86 DWT
  last column) and its follow-ups: were affected, fixed, with the code and
  tests that hold each fix.

docs/state.md records #1566 under "Confirmed not-affected".
lusoris pushed a commit to Tualua/vmafx that referenced this pull request Oct 6, 2026
… defects on the known-upstream page (VMAFx#2178)

* docs(upstream): record the CUDA 16-bit row-stride and integer ADM GPU defects on the known-upstream page

The known-upstream page listed VMAFx#1562 only. It now has a dated section for
the GPU reports checked on 2026-10-05:

- VMAFx#1566 (fixed upstream by VMAFx#1552): the CUDA motion kernel above 8 bits
  advanced a 16-bit pointer by the byte stride. Not affected: the fork's
  SAD kernel reads a row through a byte pointer (load_sample()), equal to
  the CPU in test_cuda_exact_twins, test_cuda_motion_tiny_frames and the
  depth and layout matrix; the planted upstream form fails above 8 bits and
  gives 26993 invalid reads under compute-sanitizer memcheck.
- VMAFx#1564 bugs 1 to 3 (CUDA masking border rows, per-warp rounding, x86 DWT
  last column) and its follow-ups: were affected, fixed, with the code and
  tests that hold each fix.

docs/state.md records VMAFx#1566 under "Confirmed not-affected".
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies security type:chore Maintenance, no user-visible change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant