act 0.2.81 through 0.2.89 Missing Authorization in the Artifacts V4 Backend (CVE-2026-76847) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-76847

act 0.2.81 through 0.2.89 Missing Authorization in the Artifacts V4 Backend

Answer in brief

CVE-2026-76847 records a Unknown severity vulnerability in act 0.2.81 through 0.2.89 Missing Authorization in the Artifacts V4 Backend. The current sources do not mark it as known exploited. The current feed maps nektos/act (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 24, 2026Updated Aug 24, 2026Source checked Aug 24, 2026First seen by HOL Aug 24, 2026Material review Aug 24, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps nektos/act (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
nektos/actgeneric	0.2.81	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for nektos/act.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Aug 24, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 24, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 24, 2026

Sources and claim methodology

Upstream source description

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 DeleteArtifact, accept a caller-supplied workflow_run_backend_id and never check that it belongs to the requester: validateRunIDV4 in pkg/artifacts/artifacts_v4.go parses the value and returns it with the comparison against the requesting task's run ID left commented out. The signed URLs the backend issues are authenticated by an HMAC whose key is hardcoded to the four bytes 0xba 0xdb 0xee 0xf0, identical in every build, computed over a concatenation of endpoint, expiry, artifact name and task ID with no length prefix or delimiter, so signatures are both forgeable and ambiguous between differing artifact name and task ID pairs. The --artifact-server-addr flag defaults to the host's outbound address rather than loopback, leaving the backend reachable from the surrounding network. Any client that can reach it may read, overwrite or delete the artifacts of a concurrently running job with no credentials, exposing build outputs such as secrets and deployment credentials and permitting their replacement before the owning job consumes them.

Quoted source text, attributed separately from HOL analysis.