https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 13 Oct 2026 01:19:41 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-310000 EUVD-2026-310000 https://cve.radiocsirt.org/vuln/euvd-2026-310000 https://cve.radiocsirt.org/vuln/fkie_cve-2026-42301 <p>pyp2spec generates working Fedora RPM spec file for Python projects. Prior to version 0.14.1, 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. This issue has been patched in version 0.14.1.</p> <p>pyp2spec generates working Fedora RPM spec file for Python projects. Prior to version 0.14.1, 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. This issue has been patched in version 0.14.1.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-42301 https://cve.radiocsirt.org/vuln/ghsa-r35x-v8p8-xvhw <p><strong>Affected:</strong> PyPI: pyp2spec</p> <p>### 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.</p> <p>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&#39;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&#39;s workstation enables committing malicious source to dist-git and riding it through the normal build pipeline to end users.</p> <p>### Patches Patched in 0.14.1.</p> <p>### Workarounds None</p> <p><strong>Affected:</strong> PyPI: pyp2spec</p> <p>### 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.</p> <p>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&#39;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&#39;s workstation enables committing malicious source to dist-git and riding it through the normal build pipeline to end users.</p> <p>### Patches Patched in 0.14.1.</p> <p>### Workarounds None</p> https://cve.radiocsirt.org/vuln/ghsa-r35x-v8p8-xvhw https://cve.radiocsirt.org/vuln/pysec-2026-3003 <p><strong>Affected:</strong> PyPI: pyp2spec</p> <p>### 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.</p> <p>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&#39;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&#39;s workstation enables committing malicious source to dist-git and riding it through the normal build pipeline to end users.</p> <p>### Patches Patched in 0.14.1.</p> <p>### Workarounds None</p> <p><strong>Affected:</strong> PyPI: pyp2spec</p> <p>### 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.</p> <p>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&#39;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&#39;s workstation enables committing malicious source to dist-git and riding it through the normal build pipeline to end users.</p> <p>### Patches Patched in 0.14.1.</p> <p>### Workarounds None</p> https://cve.radiocsirt.org/vuln/pysec-2026-3003