CVE-2026-91187: CWE-347 Improper Verification of Cryptographic Signature in dashbit nimble_zta
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.
AI Analysis
Technical Summary
The vulnerability in dashbit nimble_zta (versions >=0.1.2 <0.1.3) is due to improper verification of cryptographic signatures (CWE-347). Specifically, the verify_token/2 function in lib/nimble_zta/cloudflare.ex incorrectly handles the result of JOSE.JWT.verify/2 by ignoring the boolean verification outcome and returning the decoded token even if signature verification fails. An attacker can exploit this by sending a forged JWT in the cf-access-jwt-assertion header with the expected issuer and service token claims, which the system then accepts as authenticated identity. This allows unauthenticated remote attackers to authenticate as arbitrary Cloudflare service tokens.
Potential Impact
An unauthenticated remote attacker can bypass signature verification and impersonate any Cloudflare service token, potentially gaining unauthorized access to resources protected by the Cloudflare Zero Trust authentication strategy. This represents a critical security risk due to the complete bypass of authentication controls.
Mitigation Recommendations
A patch is available for this vulnerability. Users should upgrade nimble_zta to version 0.1.3 or later where this issue is fixed. Since this is a cloud service-related component, verify with the vendor whether the cloud-hosted service has been updated accordingly. No additional mitigation steps are indicated beyond applying the official fix.
CVE-2026-91187: CWE-347 Improper Verification of Cryptographic Signature in dashbit nimble_zta
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.
CVSS v4.0
Score 9.3critical
Affected software
dashbit
nimble_zta
dashbit
nimble_zta
cpe:2.3:a:dashbit:nimble_zta:*:*:*:*:*:*:*:*Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in dashbit nimble_zta (versions >=0.1.2 <0.1.3) is due to improper verification of cryptographic signatures (CWE-347). Specifically, the verify_token/2 function in lib/nimble_zta/cloudflare.ex incorrectly handles the result of JOSE.JWT.verify/2 by ignoring the boolean verification outcome and returning the decoded token even if signature verification fails. An attacker can exploit this by sending a forged JWT in the cf-access-jwt-assertion header with the expected issuer and service token claims, which the system then accepts as authenticated identity. This allows unauthenticated remote attackers to authenticate as arbitrary Cloudflare service tokens.
Potential Impact
An unauthenticated remote attacker can bypass signature verification and impersonate any Cloudflare service token, potentially gaining unauthorized access to resources protected by the Cloudflare Zero Trust authentication strategy. This represents a critical security risk due to the complete bypass of authentication controls.
Mitigation Recommendations
A patch is available for this vulnerability. Users should upgrade nimble_zta to version 0.1.3 or later where this issue is fixed. Since this is a cloud service-related component, verify with the vendor whether the cloud-hosted service has been updated accordingly. No additional mitigation steps are indicated beyond applying the official fix.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- EEF
- Date Reserved
- 2026-09-15T15:30:01.892Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Is Cloud Service
- true
Threat ID: 6ab526a2f7a7c541065eaeae
Added to database: 09/24/2026, 13:33:22 UTC
Last enriched: 09/24/2026, 13:47:44 UTC
Last updated: 09/25/2026, 02:46:01 UTC
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.