Notifications
Clear all
Topic starter
09/06/2026 11:42 pm
TL;DR: A CVE-2026-46354 flaw in Coder lets an unauthenticated attacker forge a PKCS#7 envelope, obtain a workspace agent session token, and potentially steal Git SSH keys and OAuth credentials from Azure-backed development workspaces, according to Orca Security. The issue shows how instance-identity trust can become secret-exposure risk when signature verification is incomplete.
NHIMG editorial — based on content published by Orca Security: the Coder vulnerability affecting Azure instance identity authentication and workspace agent secrets
By the numbers:
- CVE-2026-46354 carries a CVSS score of 9.1.
- v2.33.0-rc.0 through v2.33.2, ions v2.33.0-rc.0 through v2.33.2, v2.32.0-rc.0 through v2.32.1, v2.31.0 through v2.31.11, v2.30.0 through v2.30.7, v2.29.0 through v2.29.12, and all versions prior to v2.24.5.
Questions worth separating out
Q: What breaks when a workspace identity flow accepts forged identity data?
A: The trust boundary collapses before authentication ever occurs.
Q: Why do developer workspaces create supply-chain risk when identity is misvalidated?
A: Because workspace identities often bridge into Git repositories, OAuth-connected services, and CI/CD systems.
Q: How can security teams know whether workspace agent tokens are being over-trusted?
A: Look for token issuance paths that are not tied to strong proof of origin, and then test whether those tokens can reach secrets, repositories, or pipelines without additional checks.
Practitioner guidance
- Disable Azure instance identity authentication where it is not essential Remove the unauthenticated trust path from Coder deployments until patched versions are in place, and confirm that the configuration change is applied consistently across all environments.
- Patch every affected Coder version immediately Move to the fixed releases listed by the vendor, then inventory any downstream workspaces that may still be running versions older than v2.24.5 or within the affected release bands.
- Treat workspace agent tokens as high-risk credentials Log issuance, correlate it with runtime reachability, and alert on unusual token creation from internet-facing or unexpected workspace identities before repository access is exercised.
What's in the full article
Orca Security's full article covers the operational detail this post intentionally leaves for the source:
- Affected Coder version ranges and the exact patched releases organisations should target
- Step-by-step exploit mechanics for the forged PKCS#7 envelope and vmId prerequisite
- Temporary workaround guidance for disabling Azure instance identity authentication
- Exposure context for internet-facing deployments and why reachability changes priority
👉 Read Orca Security's analysis of the Coder PKCS#7 bypass and Azure workspace identity flaw →
Coder Azure instance identity bypass: what IAM teams need to know?
Explore further
10/06/2026 2:08 am
Instance identity is only safe when the entire cryptographic object is verified. This flaw shows that checking certificate lineage without validating the envelope signature leaves a false sense of assurance. The control failed at the trust boundary, not at privilege management, which means the security model trusted metadata instead of proof. Practitioners should read this as a verification failure, not a configuration mistake.
A few things that frame the scale:
- 85% of organisations lack full visibility into third-party vendors connected via OAuth apps, according to The State of Non-Human Identity Security.
- Only 1.5 out of 10 organisations are highly confident in their ability to secure NHIs, compared with nearly 1 in 4 for securing human identities.
A question worth separating out:
Q: Who is accountable when an unauthenticated workspace identity flaw exposes secrets?
A: Accountability sits with the platform owner first, then with the teams responsible for identity validation, secret access, and downstream integration governance. In regulated or audited environments, the control failure also belongs in incident reporting because it can affect source code, credentials, and operational resilience.
👉 Read our full editorial: Coder PKCS#7 bypass exposes workspace agent secrets on Azure
