{"answers":{"affected":"1 open source package ship an affected version, including OZI-Project/publish.","exploited":"There is no known exploitation of CVE-2025-47271 in the wild and no public exploit code.","fix":"Upgrade OZI-Project/publish to 1.13.6 or later.","what":"CVE-2025-47271 is a medium-severity code injection vulnerability in OZI-Project publish, published on 12 May 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-47271 and fix it if it is affected.\n\nWhat it is: CVE-2025-47271 is a medium-severity code injection vulnerability in OZI-Project publish, published on 12 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-47271 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- OZI-Project/publish (GitHub Actions): affected from 1.13.2; fixed in 1.13.6\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-2025-47271/ (Markdown: https://insights.sbomify.com/CVE-2025-47271/index.md)","id":"CVE-2025-47271","markdown":"https://insights.sbomify.com/CVE-2025-47271/index.md","name":"CVE-2025-47271","record":{"aliases":["GHSA-2487-9f55-2vg9"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"GitHub Action","requires_auth":"low_privilege","summary":"A malicious actor can inject arbitrary code via branch names in the OZI-Project publish GitHub Action, leading to code execution.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U","version":"4.0"},"cwes":[{"id":"CWE-95","name":"Improper Neutralization of Directives in Dynamically Evaluated Code"},{"id":"CWE-94","name":"Improper Control of Generation of Code"},{"id":"CWE-1116","name":"Inaccurate Source Code Comments"}],"description":"The OZI action is a GitHub Action that publishes releases to PyPI and mirror releases, signature bundles, and provenance in a tagged release. In versions 1.13.2 through 1.13.5, potentially untrusted data flows into PR creation logic. A malicious actor could construct a branch name that injects arbitrary code. This is patched in 1.13.6. As a workaround, one may downgrade to a version prior to 1.13.2.","ecosystems":["GitHub Actions"],"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":"OZI-Project/ozi-publish Code Injection vulnerability","id":"CVE-2025-47271","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"GitHub Actions","product":null,"products":[],"type":"code_injection","year":"2025"},"n_packages":1,"n_references":2,"next":{"headline":"PhoenixCart Vulnerable to Account Deletion Without Password Confirmation","id":"CVE-2025-47272"},"packages":[{"ecosystem":"GitHub Actions","fixed":["1.13.6"],"introduced":["1.13.2"],"last_affected":[],"package":"OZI-Project/publish","purl":null,"source":"GHSA-2487-9f55-2vg9"}],"prev":{"headline":"nimiq-network-libp2p Uncontrolled Resource Consumption vulnerability","id":"CVE-2025-47270"},"products":["publish"],"published":"2025-05-12","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":"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":"2025-05-12","vendors":["OZI-Project"]},"summary":"A malicious actor can inject arbitrary code via branch names in the OZI-Project publish GitHub Action, leading to code execution.","url":"https://insights.sbomify.com/CVE-2025-47271/"}