CVE-2026-46354
Coder: PKCS#7 signature bypass in Azure instance identity allows unauthenticated agent token theft
Description
Coder allows organizations to provision remote development environments via Terraform. In versions prior tp 2.24.5, 2.29.13, 2.30.8, 2.31.12, 2.32.2, and 2.33.3, `azureidentity.Validate()` verifies that the PKCS#7 signer certificate chains to a trusted Azure CA but never verifies the PKCS#7 signature itself. An attacker can embed a legitimate Azure certificate alongside arbitrary content e.g. `{"vmId":"<target>"}` and the forged `vmId` will be accepted returning the victim workspace agent's session token. No authentication is required. The attacker only needs to know a target VM's `vmId` which is a `UUIDv4`. That's a practical limitation which would typically require prior access to be exploited. Versions 2.24.5, 2.29.13, 2.30.8, 2.31.12, 2.32.2, and 2.33.3 patch the issue. As a workaround, reconfigure any Azure templates to use token authentication rather than `azure-instance-identity`.
INFO
Published Date :
July 7, 2026, 10:16 p.m.
Last Modified :
July 7, 2026, 10:16 p.m.
Remotely Exploit :
Yes !
Source :
[email protected]
Affected Products
The following products are affected by CVE-2026-46354
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | CRITICAL | [email protected] |
Solution
- Update Coder to version 2.24.5 or later.
- Reconfigure Azure templates to use token authentication.
- Disable azure-instance-identity authentication method.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-46354.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-46354 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-46354
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-46354 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-46354 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by [email protected]
Jul. 07, 2026
Action Type Old Value New Value Added Affected [{'vendor': 'coder', 'product': 'coder', 'versions': [{'status': 'affected', 'version': '>= 2.33.0-rc.0, < 2.33.3'}, {'status': 'affected', 'version': '>= 2.32.0-rc.0, < 2.32.2'}, {'status': 'affected', 'version': '>= 2.31.0, < 2.31.12'}, {'status': 'affected', 'version': '>= 2.30.0, < 2.30.8'}, {'status': 'affected', 'version': '>= 2.29.0, < 2.29.13'}, {'status': 'affected', 'version': '< 2.24.5'}]}] Added Description Coder allows organizations to provision remote development environments via Terraform. In versions prior tp 2.24.5, 2.29.13, 2.30.8, 2.31.12, 2.32.2, and 2.33.3, `azureidentity.Validate()` verifies that the PKCS#7 signer certificate chains to a trusted Azure CA but never verifies the PKCS#7 signature itself. An attacker can embed a legitimate Azure certificate alongside arbitrary content e.g. `{"vmId":"<target>"}` and the forged `vmId` will be accepted returning the victim workspace agent's session token. No authentication is required. The attacker only needs to know a target VM's `vmId` which is a `UUIDv4`. That's a practical limitation which would typically require prior access to be exploited. Versions 2.24.5, 2.29.13, 2.30.8, 2.31.12, 2.32.2, and 2.33.3 patch the issue. As a workaround, reconfigure any Azure templates to use token authentication rather than `azure-instance-identity`. Added CVSS V3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N Added CWE CWE-347 Added Reference https://github.com/coder/coder/pull/25286 Added Reference https://github.com/coder/coder/releases/tag/v2.24.5 Added Reference https://github.com/coder/coder/releases/tag/v2.29.13 Added Reference https://github.com/coder/coder/releases/tag/v2.30.8 Added Reference https://github.com/coder/coder/releases/tag/v2.31.12 Added Reference https://github.com/coder/coder/releases/tag/v2.32.2 Added Reference https://github.com/coder/coder/releases/tag/v2.33.3 Added Reference https://github.com/coder/coder/security/advisories/GHSA-6x44-w3xg-hqqf