HOMEVULNERABILITIESCVE-2026-46354
CRITICAL

CVE-2026-46354

CWE-347Published: July 7, 2026· Updated: Jul 8, 2026

9.1
CVSS v3.1
EPSS:0.26%probability of exploitation in 30 daysPercentile:17.6th

Official 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`.

NVD Source

Risk Analysis

This critical vulnerability in Coder allows an unauthenticated attacker to obtain a victim workspace agent's session token. The flaw lies in the `azureidentity.Validate()` function, which fails to verify the PKCS#7 signature, allowing forged `vmId` values to be accepted. With a CVSS score of 9.1, this vulnerability presents a high risk of unauthorized access.

Currently, there are no public exploits known for this vulnerability. While unauthenticated, exploitation requires knowing a target VM's `vmId`, which is a UUIDv4, making it a practical limitation.

Recommended Action

Upgrade Coder to versions 2.24.5, 2.29.13, 2.30.8, 2.31.12, 2.32.2, or 2.33.3 to patch this issue. As a defense-in-depth measure, restrict access to `vmId` information.

Generated by the CTIWATCH analysis pipeline from this CVE's metadata (CVSS, EPSS, KEV status, exploit intelligence). Verify against vendor advisories before acting.

Technical Analysis

CVE-2026-46354 can be exploited remotely over the network without requiring physical or adjacent access, significantly expanding the attack surface for threat actors.

The vulnerability requires no privileges and no user interaction, making it a prime target for automated exploitation campaigns and worm-like propagation.

A successful exploit results in complete confidentiality breach (data exposure), full integrity compromise (data manipulation), with a CVSS base score of 9.1.

CVSS v3.1 Vector Breakdown

Exploitability
Attack VectorNetwork
Attack ComplexityLow
Privileges Req.None
User InteractionNone
ScopeUnchanged
Impact
ConfidentialityHigh
IntegrityHigh
AvailabilityNone
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected Vendors & Products

coder1 product(s)
coder
Source: NVD CPE · 1 total CPE entries

Exploit & PoC Resources

NO KNOWN EXPLOITNo public exploit confirmed at this time
External links open in a new tab. Always verify in a controlled environment before use.

Official Patches & Advisories

All References (8)

Quick Facts

CVE IDCVE-2026-46354
CVSS Score9.1 / 10
SeverityCRITICAL
WeaknessCWE-347
CISA KEVNo
EPSS (30d)0.26%
Affected1 vendor(s)
PublishedJul 7, 2026

Related CVEs (CWE-347)

Recommended Actions

  • Apply vendor patches immediately
  • Monitor CVE-2026-46354 in threat intel feeds
  • Review IDS/IPS signatures for exploitation attempts
Data sourced from NVD (NIST), CISA KEV, and EPSS (FIRST). Analysis generated by CTIWATCH.COM. CVE data is provided under the NVD usage policy.