<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Nektos - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/vendors/nektos/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Mon, 24 Aug 2026 16:02:45 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/vendors/nektos/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>Authentication Bypass and Artifact Manipulation in 'act' HTTP Artifacts V4 Backend</title><link>https://feed.craftedsignal.io/briefs/2026-08-act-artifacts-v4-auth-bypass/</link><pubDate>Mon, 24 Aug 2026 16:02:45 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-08-act-artifacts-v4-auth-bypass/</guid><description>The 'act' tool's HTTP Artifacts V4 backend suffers from an authentication bypass and hardcoded HMAC key vulnerability (CVE-2026-76847), allowing unauthorized network actors to access, modify, or delete artifacts and exfiltrate secrets.</description><content:encoded><![CDATA[<p>The 'act' tool, used for running GitHub Actions locally, exposes a critical security vulnerability (CVE-2026-76847) in its HTTP Artifacts V4 backend implementation. Introduced to support actions/upload-artifact@v4 and actions/download-artifact@v4, this backend fails to validate the <code>workflow_run_backend_id</code> parameter against the requesting task, essentially disabling access control. Furthermore, the backend uses a static, hardcoded four-byte HMAC key (0xba 0xdb 0xee 0xf0) for signing artifact URLs. The flawed construction of these signatures, combined with the fact that the artifact server defaults to listening on all network interfaces rather than loopback, allows any reachable attacker to read, overwrite, or delete build artifacts. This vulnerability enables the theft of sensitive data such as hardcoded secrets, API keys, or deployment credentials, and allows attackers to inject malicious files into the CI/CD pipeline of a target machine.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows for the complete compromise of CI/CD build outputs handled by the 'act' tool. Unauthorized actors can exfiltrate sensitive environment variables, deployment tokens, and build artifacts, or manipulate files to facilitate supply-chain attacks on build processes. Given the hardcoded key and lack of network binding restrictions, any attacker with network visibility to the host running 'act' can perform these operations without credentials.</p>
<h2 id="recommendation">Recommendation</h2>
<p>Prioritized, concrete actions for detection engineering and security teams:</p>
<ul>
<li>Update the 'act' tool to the latest patched version immediately to resolve CVE-2026-76847.</li>
<li>Inspect existing network configurations for hosts running 'act'; ensure that artifact server ports are not exposed to untrusted networks.</li>
<li>Implement network-level egress and ingress filtering to restrict access to the 'act' artifact server port (typically configured via <code>--artifact-server-addr</code>) to localhost only.</li>
<li>Audit CI/CD logs for unauthorized access to artifact endpoints or unexpected artifact modification events if the tool was previously deployed in a shared or non-isolated environment.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item></channel></rss>