CVE-2025-30154
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedreviewdog/action-setup is a GitHub action that installs reviewdog. reviewdog/action-setup@v1 was compromised March 11, 2025, between 18:42 and 20:31 UTC, with malicious code added that dumps exposed secrets to Github Actions Workflow Logs. Other reviewdog actions that use `reviewdog/action-setup@v1` that would also be compromised, regardless of version or pinning method, are reviewdog/action-shellcheck, reviewdog/action-composite-template, reviewdog/action-staticcheck, reviewdog/action-ast-grep, and reviewdog/action-typos.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe reviewdog/action-setup@v1 GitHub Action was compromised for approximately 2 hours on March 11, 2025, with malicious code added that exfiltrates exposed secrets to GitHub Actions Workflow Logs. This supply chain compromise affects not only action-setup@v1 but also five dependent reviewdog actions (shellcheck, composite-template, staticcheck, ast-grep, typos) regardless of version pinning.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.26.2< 0.20.2= 1< 1.29.2< 1.26.2< 1.17.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if reviewdog/action-setup@v1 is used in workflowsSearch workflow YAML files (.github/workflows/*.yml) for 'uses: reviewdog/action-setup@v1' or 'uses: reviewdog/action-setup@1'Affected if The workflow file references reviewdog/action-setup@v1 or @1 without a specific version/commit hash that is confirmed safe
-
Identify dependent reviewdog actions usedSearch workflow files for: reviewdog/action-shellcheck, reviewdog/action-composite-template, reviewdog/action-ast-grep, reviewdog/action-staticcheck, reviewdog/action-typos - note the version tags (e.g., @1.29.1, @1.26.1)Affected if Any of these actions are used with versions below the patched releases (Shellcheck <1.29.2, Staticcheck <1.26.2, Ast Grep <1.26.2, Typos <1.17.2, Composite Template <0.20.2)
-
Check workflow run timestamps against compromise windowIn GitHub, navigate to repository Settings > Actions > Workflow run history, filter runs between March 11, 2025 18:42 and 20:31 UTCAffected if Any workflows using the affected reviewdog actions ran during this time window
-
Inspect workflow run logs for secret exfiltration indicatorsReview action logs from the compromise window for unusual patterns: base64-encoded strings, unexpected HTTP POST/GET requests to external domains, or secrets appearing in log output that were not intentionally printedAffected if Logs contain suspicious data transfers, base64 strings, or credentials that were exposed
-
Audit GitHub secrets and tokens used in affected workflowsIn GitHub repository Settings > Secrets and variables > Actions, review all secrets used in workflows that ran during the compromise windowAffected if Any secrets or tokens were used in workflows that executed during March 11, 2025 18:42-20:31 UTC
A user is affected if their workflows used any vulnerable reviewdog action versions or action-setup@v1 and executed between March 11, 2025 18:42-20:31 UTC, or if workflow logs show evidence of secret exfiltration.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.20.21.17.21.26.2
Organizations must immediately revoke any secrets that may have been exposed in workflow logs during the compromise window (March 11, 2025 18:42-20:31 UTC), audit all CI/CD pipelines for usage of the six affected reviewdog actions, and update to non-compromised versions or remove the compromised dependency.
reviewdog/action-setup@v2+ (or latest); [email protected]+; [email protected]+; [email protected]+; [email protected]+; [email protected]+
- 1. Upgrade reviewdog/action-setup from v1 to the latest version (v2 or higher recommended) - this is the primary fix as it removes the compromised dependency
- 2. Upgrade reviewdog/action-ast-grep to version 1.26.2 or later
- 3. Upgrade reviewdog/action-composite-template to version 0.20.2 or later
- 4. Upgrade reviewdog/action-shellcheck to version 1.29.2 or later
- 5. Upgrade reviewdog/action-staticcheck to version 1.26.2 or later
- 6. Upgrade reviewdog/action-typos to version 1.17.2 or later
- 7. Review GitHub Actions workflow logs from March 11, 2025 between 18:42-20:31 UTC for any unauthorized secret exfiltration
- 8. Rotate any secrets, tokens, or credentials that may have been exposed during the compromise window
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30154 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-30154 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data