tj-actions changed-files through 45.0.7 allows remote attackers to discover secrets by reading actions logs.

Exploitation

Confirmed: listed in the CISA Known Exploited Vulnerabilities catalog.

CVSS

8.6 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N/E:H

EPSS

• CVE-2025-30066: 72.09% estimated exploitation activity in the next 30 days; percentile 99.43 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary A supply chain attack compromised the tj-actions/changed-files GitHub Action, impacting over 23,000 repositories. Attackers retroactively modified multiple version tags to reference a malicious commit, exposing CI/CD secrets in workflow logs. The vulnerability existed between March 14 and March 15, 2025, and has since been mitigated. This poses a significant risk of unauthorized access to sensitive information. This has been patched in v46.0.1. Details The attack involved modifying the tj-actions/changed-files GitHub Action to execute a malicious Python script. This script extracted secrets from the Runner Worker process memory and printed them in GitHub Actions logs, making them publicly accessible in repositories with public workflow logs. Key Indicators of Compromise (IoC): - Malicious commit: 0e58ed8671d6b60d0890c21b07f8835ace038e67 - Retroactively updated tags pointing to the malicious commit: - v1.0.0: 0e58ed8671d6b60d0890c21b07f8835ace038e67 - v35.7.7-sec:…

Published by the source

15 Mar 2025, 06:30 UTC

Last modified by the source

22 Oct 2025, 19:29 UTC

Source last checked

26 Oct 2026, 17:08 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-mrrh-fwg8-r2c3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-30066

Advisory: tj-actions changed-files through 45.0.7 allows remote attackers to discover secrets by reading actions logs.
IDs: CVE-2025-30066, GHSA-mrrh-fwg8-r2c3
Record: https://patchnext.com/advisories/cve-2025-30066 (revision 1, source checked 26 Oct 2026, 17:08 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.6)
Exploitation: confirmed: listed in the CISA Known Exploited Vulnerabilities catalog.
Vendor response: Vendor fix available; fixed versions by package: tj-actions/changed-files 46.0.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- GitHub Actions tj-actions/changed-files: affected <= 45.0.7; fixed in 46.0.1

## Suggested inspection (read-only)
- GitHub Actions tj-actions/changed-files: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on tj-actions/changed-files.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://www.cisa.gov/known-exploited-vulnerabilities-catalog (CISA added CVE-2025-30066 to the Known Exploited Vulnerabilities catalog on 2025-03-18.)
- Verified: https://github.com/advisories/GHSA-mrrh-fwg8-r2c3 (GitHub-reviewed advisory GHSA-mrrh-fwg8-r2c3 lists affected ranges: GitHub Actions tj-actions/changed-files >=0 <=45.0.7)

Commands are suggestions: review each one before running it.