CVE-2026-91187

published 24 Sep 2026 · updated 19 Nov 2026

Improper Verification of Cryptographic Signature in dashbit nimble_zta Cloudflare strategy

9.3CriticalCVSS 9.3EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 0.1.3 and 6458fd18a5ba41166d4973214c519e98fe05b72d.

Improper Verification of Cryptographic Signature vulnerability in dashbit nimble_zta allows an unauthenticated remote attacker to authenticate as an arbitrary Cloudflare service token. Applications using the Cloudflare Zero Trust authentication strategy are affected. verify_token/2 in lib/nimble_zta/cloudflare.ex matches the result of JOSE.JWT.verify/2 against {_, token, _s}, which discards the boolean verification result and returns the decoded token after a failed signature check. The attacker sends a forged JWT in the cf-access-jwt-assertion header, carrying the expected iss claim and the seven service token claims. verify_iss/2 reads the iss claim from the forged token, so it rejects nothing, and the service token path then returns those claims as the authenticated identity. This issue affects nimble_zta: from 0.1.2 before 0.1.3.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
dashbit>=0.1.2 <0.1.3, >=bc004b70985ae5763901baab3a4e204047899768 <6458fd18a5ba41166d4973214c519e98fe05b72d0.1.3, 6458fd18a5ba41166d4973214c519e98fe05b72d

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-91187 severity on Zeptric[![CVE-2026-91187](https://zeptric.io/badge/cve/CVE-2026-91187.svg)](https://zeptric.io/cve/CVE-2026-91187)