All vulnerabilities
CVE-2026-91187GHSA-rj24-g8cc-g7g2

Improper Verification of Cryptographic Signature in dashbit nimble_zta Cloudflare strategy

dashbit nimble_zta
CVSS
9.3Critical
ExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)0.30%Chance of exploitation activity in the next 30 days, higher than 21% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed in0.1.3Also 6458fd18a5ba41166d4973214c519e98fe05b72dCVE List
Published24 Sep 2026Updated 24 Sep 2026CVE List

What fixes it

  • 0.1.3nimble_ztaCVE List
  • 6458fd18a5ba41166d4973214c519e98fe05b72dnimble_ztaCVE List

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

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.

Text from CVE List

Affected versions 2

  • nimble_ztaaffected: 0.1.2 before 0.1.3CVE List
  • nimble_ztaaffected: bc004b70985ae5763901baab3a4e204047899768 before 6458fd18a5ba41166d4973214c519e98fe05b72dCVE List

References 5