Artifact theft and replacement via unchecked run identifiers
Published Aug 24, 2026 · Updated Aug 24, 2026
Missing authorization in Nektos act 0.2.81 through 0.2.89 allows remote attackers to read, overwrite, or delete workflow artifacts. validateRunIDV4 accepts caller-supplied run identifiers without ownership checks, while signed artifact URLs use a shared four-byte HMAC key over ambiguous concatenated fields. Exploitation requires network access to a running Artifacts V4 backend and exposes or replaces build outputs, including stored deployment credentials.
Summary
What happened
Missing authorization in Nektos act 0.2.81 through 0.2.89 allows remote attackers to read, overwrite, or delete workflow artifacts. validateRunIDV4 accepts caller-supplied run identifiers without ownership checks, while signed artifact URLs use a shared four-byte HMAC key over ambiguous concatenated fields. Exploitation requires network access to a running Artifacts V4 backend and exposes or replaces build outputs, including stored deployment credentials.
The record
- CVE
- CVE-2026-76847
- Published
- Aug 24, 2026
- Updated
- Aug 24, 2026
- Vendor
- Nektos
- Product
- act
- Classifications
- CWE-862, CWE-321, T1552.001, T1190, T1565.001
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 24, 2026CVE publishedPublication date reported by the CVE source.
- Aug 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.2.81 <=0.2.89
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo