Nektos vulnerabilities
We track 4 vulnerabilities in Nektos products. 4 are rated high or critical, and none are known to be exploited. The most recent was published on August 24, 2026.
Latest Nektos vulnerabilities
- 8.8 High severity
act: Use of Hard-coded Cryptographic Key
act starts an HTTP Artifacts V4 backend whenever a workflow uses actions/upload-artifact@v4 or actions/download-artifact@v4. The control-plane RPCs of that backend, including CreateArtifact, GetSignedArtifactURL, ListArtifacts, FinalizeArtifact and DeleteArtif
- 8.2 High severity
act: Missing Authorization
act is a project which allows for local running of github actions. Prior to version 0.2.86, act's built in actions/cache server listens to connections on all interfaces and allows anyone who can connect to it including someone anywhere on the internet to creat
- 7.7 High severity
act: Improper Neutralization of Special Elements in Output Used by a Downstream Component
act is a project which allows for local running of github actions. Prior to version 0.2.86, act unconditionally processes the deprecated ::set-env:: and ::add-path:: workflow commands, which was disabled due to environment injection risks. When a workflow step
- 8.8 High severity
act: Improper Limitation of a Pathname to a Restricted Directory
act is a project which allows for local running of github actions. The artifact server that stores artifacts from Github Action runs does not sanitize path inputs. This allows an attacker to download and overwrite arbitrary files on the host from a Github Acti