Intel

AIKIDO-2026-321692

github.com/nektos/act is vulnerable to Use of Hard-coded Cryptographic Key

CVE-2026-76847Published 4 days ago
November 16, 2026

88

CVE Score

High

Use of Hard-coded Cryptographic Key

Are you affected? Scan for Free

TL;DR

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.

How do I fix this?

Upgrade the github.com/nektos/act library to the patch version.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range and run workflows using the Artifacts V4 backend.

Versions

0.2.63 - 0.2.89

Fixed in 0.2.90

Background info

github.com/nektos/act is vulnerable to Use of Hard-coded Cryptographic Key in versions 0.2.63 - 0.2.89.

Get secure today,
quickly and for free.

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.

Trusted by 150k+ orgs
  • Revolut
  • n8n
  • Lovable
  • Deel
  • Prove
  • Omnea