Description
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 products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| dashbit | nimble_zta | 0.1.2 – < 0.1.3 | 0.1.3 |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| Hex | nimble_zta | >= 0.1.2, < 0.1.3 | 0.1.3 | EEF-CVE-2026-91187 |
References
- GitHub Advisory related vendor-advisory
- EEF CNA record for CVE-2026-91187 related
- OSV record EEF-CVE-2026-91187 related
- Introducing commit bc004b7 in dashbitco/nimble_zta related
- Fix commit 6458fd1 in dashbitco/nimble_zta patch