CVE-2026-46354

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 82% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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":""} 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.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
56(Track)
EG Risk 56/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
17.6%
KEV
Not listed

Published

May 19, 2026

Last Modified

July 8, 2026

Advisory Details (8)

Auto-updated Jul 7, 2026
Patch available. Sources: github_pr, github_release, github.
github Patch Available

PKCS#7 signature bypass in Azure instance identity allows unauthenticated agent token theft · Advisory · coder/coder · GitHub

https://github.com/coder/coder/security/advisories/GHSA-6x44-w3xg-hqqf
github_release Patch Available

v2.33.3

Patch available: coder/coder v2.33.3

https://github.com/coder/coder/releases/tag/v2.33.3
github_release Patch Available

v2.32.2

Patch available: coder/coder v2.32.2

https://github.com/coder/coder/releases/tag/v2.32.2
github_release Patch Available

v2.31.12

Patch available: coder/coder v2.31.12

https://github.com/coder/coder/releases/tag/v2.31.12
github_release Patch Available

v2.30.8

Patch available: coder/coder v2.30.8

https://github.com/coder/coder/releases/tag/v2.30.8
github_release Patch Available

v2.29.13

Patch available: coder/coder v2.29.13

https://github.com/coder/coder/releases/tag/v2.29.13
github_release Patch Available

v2.24.5

Patch available: coder/coder v2.24.5

https://github.com/coder/coder/releases/tag/v2.24.5
github_pr

fix: verify PKCS7 signature on Azure instance identity tokens

Fix merged in coder/coder PR #25286 on 2026-05-13 — awaiting tagged release

https://github.com/coder/coder/pull/25286

Vendor Advisories for CVE-2026-46354(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 1 ecosystem)
Go(2)
PackageVulnerable rangeFixed inDependents
github.com/coder/coder———
github.com/coder/coder/v2—2.33.3—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 18× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:17 UTCEG score recompute
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:24 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-19 02:29 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-17 23:29 UTCOSV refresh
  10. 2026-07-16 17:03 UTCEPSS rescore
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-15 02:00 UTCEPSS rescore
  13. 2026-07-13 22:30 UTCEPSS rescore
  14. 2026-07-13 06:13 UTCEPSS rescore
  15. 2026-07-12 05:46 UTCEPSS rescore
  16. 2026-07-11 08:27 UTCEPSS rescore
  17. 2026-07-09 19:10 UTCEPSS rescore
  18. 2026-07-08 15:16 UTCEPSS rescore
  19. 2026-06-14 23:18 UTCEPSS rescore
  20. 2026-06-13 23:00 UTCEPSS rescore
  21. 2026-06-12 23:12 UTCEPSS rescore
  22. 2026-05-24 06:13 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-46354?
CVE-2026-46354 is a critical vulnerability published on May 19, 2026. 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…
When was CVE-2026-46354 disclosed?
CVE-2026-46354 was first published in the National Vulnerability Database on May 19, 2026, with the most recent update on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46354 actively exploited?
CVE-2026-46354 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46354?
CVE-2026-46354 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-46354?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46354, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46354

Explore →

Is Your Infrastructure Affected by CVE-2026-46354?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs