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
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
dashbit nimble_zta
Default version status: unaffected
0.1.2 to < 0.1.3affected
pkg:hex/nimble_ztadashbit nimble_zta
Default version status: unaffected
bc004b70985ae5763901baab3a4e204047899768 to < 6458fd18a5ba41166d4973214c519e98fe05b72daffected
pkg:github/dashbitco/nimble_ztaReferences
- https://github.com/dashbitco/nimble_zta/security/advisories/GHSA-rj24-g8cc-g7g2 ↗
- https://cna.erlef.org/cves/CVE-2026-91187.html ↗
- https://osv.dev/vulnerability/EEF-CVE-2026-91187 ↗
- https://github.com/dashbitco/nimble_zta/commit/bc004b70985ae5763901baab3a4e204047899768 ↗
- https://github.com/dashbitco/nimble_zta/commit/6458fd18a5ba41166d4973214c519e98fe05b72d ↗