{"answers":{"affected":"3 open source packages ship an affected version, including pyp2spec.","exploited":"There is no known exploitation of CVE-2026-42301 in the wild and no public exploit code.","fix":"Upgrade pyp2spec to 0.14.1 or later.","what":"CVE-2026-42301 is a high-severity code injection vulnerability in befeleme pyp2spec, published on 9 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-42301 and fix it if it is affected.\n\nWhat it is: CVE-2026-42301 is a high-severity code injection vulnerability in befeleme pyp2spec, published on 9 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-42301 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- pyp2spec (PyPI): affected all versions; fixed in 0.14.1\n- pyp2spec (PyPI): affected all versions; fixed in 0.14.1\n- pyp2spec (PyPI): affected all versions; fixed in 0.14.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-42301/ (Markdown: https://insights.sbomify.com/CVE-2026-42301/index.md)","id":"CVE-2026-42301","markdown":"https://insights.sbomify.com/CVE-2026-42301/index.md","name":"CVE-2026-42301","record":{"aliases":["GHSA-r35x-v8p8-xvhw","PYSEC-2026-3003"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Python RPM spec generator","requires_auth":"none","summary":"Attackers can execute arbitrary commands on build machines by injecting RPM macros into PyPI metadata processed by pyp2spec.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Improper Input Validation leading to Improper Control of Generation of Code ('Code Injection') in pyp2spec","id":"CVE-2026-42301","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"FastGPT: Unauthenticated Remote Code Execution (RCE) via code-server Misconfiguration in agent-sandbox","id":"CVE-2026-42302"},"packages":[{"ecosystem":"PyPI","fixed":["0.14.1"],"introduced":["0"],"last_affected":[],"package":"pyp2spec","purl":null,"source":"GHSA-r35x-v8p8-xvhw"},{"ecosystem":"PyPI","fixed":["0.14.1"],"introduced":["0"],"last_affected":[],"package":"pyp2spec","purl":"pkg:pypi/pyp2spec","source":"GHSA-r35x-v8p8-xvhw"},{"ecosystem":"PyPI","fixed":["0.14.1"],"introduced":["0"],"last_affected":[],"package":"pyp2spec","purl":"pkg:pypi/pyp2spec","source":"PYSEC-2026-3003"}],"prev":{"headline":"DevGuard: Unauthenticated identity assertion via `X-Admin-Token` header","id":"CVE-2026-42300"},"products":["pyp2spec"],"published":"2026-05-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-11","vendors":["befeleme"]},"summary":"Attackers can execute arbitrary commands on build machines by injecting RPM macros into PyPI metadata processed by pyp2spec.","url":"https://insights.sbomify.com/CVE-2026-42301/"}