PT-2026-59625 · Pypi · Pyp2Spec

Published 2026-07-13 · Updated 2026-07-13

OSV

CVSS v3.1

7.8

High

Base vector

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

Impact

pyp2spec was writing PyPI package metadata (e.g. the summary field) into the generated spec file without escaping RPM macro directives. When a packager then runs rpmbuild, those directives get evaluated, so a malicious package can execute arbitrary commands on the build machine.

The macro evaluates during spec parsing, not only during the build step. Any rpm tool touching the generated spec triggers execution, rpmbuild -bs, rpmbuild --nobuild, rpm -q --specfile, so the victim doesn't need to commit to a full build before getting compromised. The realistic attack path is typosquatting or targeting a package known to be under Fedora review rather than drive-by publishing. Fedora packagers hold dist-git SSH keys, Koji build credentials, and Bodhi update credentials, so compromise of one packager's workstation enables committing malicious source to dist-git and riding it through the normal build pipeline to end users.

Patches

Patched in 0.14.1.

Workarounds

None

Fix

Related Identifiers

PYSEC-2026-3003

Affected Products

Pyp2Spec

References · 7

• https://osv.dev/vulnerability/PYSEC-2026-3003 · Vendor Advisory
• https://nvd.nist.gov/vuln/detail/CVE-2026-42301 · Security Note
• https://github.com/befeleme/pyp2spec · Note
• https://github.com/befeleme/pyp2spec/security/advisories/GHSA-r35x-v8p8-xvhw · Note
• https://github.com/befeleme/pyp2spec/releases/tag/v0.14.1 · Note
• https://github.com/advisories/GHSA-r35x-v8p8-xvhw · Note
• https://pypi.org/project/pyp2spec · Note