github.com/nektos/act is vulnerable to Use of Hard-coded Cryptographic Key
88
CVE Score
High
Use of Hard-coded Cryptographic Key
When act starts the Artifacts V4 backend, its control-plane operations accept a caller-supplied workflow run backend ID without verifying ownership. The backend is reachable on the host's outbound address and uses a hard-coded signing key, allowing a reachable client to forge artifact URLs. The client can read, replace, or delete artifacts belonging to a concurrent job, exposing build outputs or affecting job integrity. The compact advisory record does not specify the remediation details.
Upgrade the github.com/nektos/act library to the patch version.
You are affected if you are using a version that falls within the vulnerable range and run workflows using the Artifacts V4 backend.
0.2.63 - 0.2.89
Fixed in 0.2.90github.com/nektos/act is vulnerable to Use of Hard-coded Cryptographic Key in versions 0.2.63 - 0.2.89.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.