Improper Verification of Cryptographic Signature in dashbit nimble_zta Cloudflare strategy
25Vexday Risk Score
Sin señal de explotación. Ningún artefacto público de explotación conocido hasta ahora.
ssvc Trackcvss 9.3
probabilidad de explotación
—
explotación observada
noninguna fuente lo reporta
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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:N
Productos afectados
dashbit · nimble_ztaReferencias
https://cna.erlef.org/cves/CVE-2026-91187.htmlhttps://github.com/dashbitco/nimble_zta/commit/6458fd18a5ba41166d4973214c519e98fe05b72dhttps://github.com/dashbitco/nimble_zta/commit/bc004b70985ae5763901baab3a4e204047899768https://github.com/dashbitco/nimble_zta/security/advisories/GHSA-rj24-g8cc-g7g2https://osv.dev/vulnerability/EEF-CVE-2026-91187