{"answers":{"affected":"1 open source package ship an affected version, including tj-actions/changed-files. It affects 1 product.","exploited":"Yes. Attackers have exploited CVE-2025-30066 in the wild since at least 18 Mar 2025.","fix":"Upgrade tj-actions/changed-files to 46.0.1 or later. US federal agencies must fix it by 8 Apr 2025.","what":"CVE-2025-30066 is a high-severity vulnerability in tj-actions changed-files, published on 15 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-30066 and fix it if it is affected.\n\nWhat it is: CVE-2025-30066 is a high-severity vulnerability in tj-actions changed-files, published on 15 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: Yes. Attackers have exploited CVE-2025-30066 in the wild since at least 18 Mar 2025.\n\nAffected packages and fixed versions:\n- tj-actions/changed-files (GitHub Actions): affected all versions; fixed in 46.0.1\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-30066/ (Markdown: https://insights.sbomify.com/CVE-2025-30066/index.md)","id":"CVE-2025-30066","markdown":"https://insights.sbomify.com/CVE-2025-30066/index.md","name":"CVE-2025-30066","record":{"aliases":["GHSA-mrrh-fwg8-r2c3"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"GitHub Actions","requires_auth":"none","summary":"Attackers can steal secrets and execute code via maliciously modified GitHub Actions tags in tj-actions changed-files.","user_interaction":"not_required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"changed-files","vendor":"tj-actions"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-506","name":"Embedded Malicious Code"}],"description":"tj-actions changed-files before 46 allows remote attackers to discover secrets by reading actions logs. (The tags v1 through v45.0.7 were affected on 2025-03-14 and 2025-03-15 because they were modified by a threat actor to point at commit 0e58ed8, which contained malicious updateFeatures code.)","ecosystems":["GitHub Actions"],"exploits":{"exploitdb":0,"first_seen":"2025-03-18","github_poc":2,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-03-18T14:33:29Z","kind":"github_poc","ref":"https://github.com/Checkmarx/Checkmarx-CVE-2025-30066-Detection-Tool","stars":1,"title":null},{"date":"2026-05-14T22:19:48Z","kind":"github_poc","ref":"https://github.com/Super-Vulnerable-Org/compromised-action","stars":0,"title":"Test repo: simulates CVE-2025-30066 style compromised GitHub Action (for security research/testing chainradar)"}],"tier":"exploited"},"has_fix":true,"headline":"tj-actions/changed-files GitHub Action Embedded Malicious Code","id":"CVE-2025-30066","indexable":true,"kev":{"dateAdded":"2025-03-18","dueDate":"2025-04-08","knownRansomwareCampaignUse":"Unknown","product":"changed-files GitHub Action","requiredAction":"Apply mitigations as set forth in the CISA instructions linked below. Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.","vendorProject":"tj-actions","vulnerabilityName":"tj-actions/changed-files GitHub Action Embedded Malicious Code Vulnerability"},"kind":"cve","links":{"ecosystem":"GitHub Actions","product":null,"products":[],"type":"supply_chain","year":"2025"},"n_packages":1,"n_references":19,"next":{"headline":"Apache Kylin: The remote code execution via jdbc url","id":"CVE-2025-30067"},"packages":[{"ecosystem":"GitHub Actions","fixed":["46.0.1"],"introduced":["0"],"last_affected":[],"package":"tj-actions/changed-files","purl":null,"source":"GHSA-mrrh-fwg8-r2c3"}],"prev":{"headline":"Apache Parquet Avro Module Vulnerable to Arbitrary Code Execution","id":"CVE-2025-30065"},"products":["changed-files"],"published":"2025-03-15","related":[{"cvss_score":7.3,"headline":"tj-actions/changed-files command injection in output filenames","id":"CVE-2023-51664","kev_date_added":null,"published":"2023-12-27"}],"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":"US public information, NVD API terms","name":"NVD"},{"class":"open","licence":"CC0 1.0","name":"CISA KEV"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"active","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["tj-actions"]},"summary":"Attackers can steal secrets and execute code via maliciously modified GitHub Actions tags in tj-actions changed-files.","url":"https://insights.sbomify.com/CVE-2025-30066/"}