Compromised GitHub action codfish/semantic-release-action steals CI/CD secrets
Attackers hijacked codfish/semantic-release-action by retagging v2–v5 to a credential-stealing payload, exposing CI/CD secrets of any project that pinned to mutable version tags.
Summary written by editorial AI · Source link below
codfish/semantic-release-action was compromised on June 24, 2026. Attackers repointed v2–v5 tags to a Miasma credential-stealing payload targeting CI/CD secrets. Here's what happened and how to check if you're affected. Category: Vulnerabilities & Threats
Editorial Analysis
This mirrors the tj-actions/changed-files incident and reinforces that pinning GitHub Actions to mutable tags is a systemic risk; any org using this action may have leaked repository secrets.
Audit CI/CD workflows for codfish/semantic-release-action usage, rotate any exposed secrets, and pin all GitHub Actions to immutable commit SHAs.
A compromised open-source CI/CD component may have exfiltrated repository credentials from any project that used it.
Forward-looking interpretation drafted by editorial AI under human review — not a reproduction of the source. See methodology.
More from the DevSecOps Desk
- Nearly 1.5 million exposed secrets targeted in new revocation program4d
- From Lab to Reality: A Practical Evaluation of Deep Learning Models and LLMs for Vulnerability Detection4d
- A.S.E 2.0: Understanding How Repository Context Impacts the Security of LLM-Generated Code4d
- A Hybrid Approach for Automated Security Pattern Recovery4d
- Chainguard endpoints now handle breaking changes5d