CVE-2026-34240: CWE-347: Improper Verification of Cryptographic Signature in appsup-dart jose
JOSE is a Javascript Object Signing and Encryption (JOSE) library. Prior to version 0.3.5+1, a vulnerability in jose could allow an unauthenticated, remote attacker to forge valid JWS/JWT tokens by using a key embedded in the JOSE header (jwk). The vulnerability exists because key selection could treat header-provided jwk as a verification candidate even when that key was not present in the trusted key store. Since JOSE headers are untrusted input, an attacker could exploit this by creating a token payload, embedding an attacker-controlled public key in the header, and signing with the matching private key. Applications using affected versions for token verification are impacted. This issue has been patched in version 0.3.5+1. A workaround for this issue involves rejecting tokens where header jwk is present unless that jwk matches a key already present in the application's trusted key store.
AI Analysis
Technical Summary
The vulnerability identified as CVE-2026-34240 affects the appsup-dart jose library, a JavaScript Object Signing and Encryption (JOSE) implementation used for handling JSON Web Tokens (JWT) and JSON Web Signatures (JWS). Prior to version 0.3.5+1, the library improperly verifies cryptographic signatures by accepting a public key embedded within the JOSE header (jwk) as a valid verification key without confirming it against a trusted key store. Since JOSE headers are untrusted input, an attacker can craft a malicious token by embedding a public key they control in the header and signing the token with the corresponding private key. The library then erroneously accepts this token as valid, enabling token forgery. This flaw corresponds to CWE-347 (Improper Verification of Cryptographic Signature). The vulnerability allows unauthenticated remote attackers to bypass authentication and authorization mechanisms in applications that rely on this library for token validation. The issue is resolved by upgrading to version 0.3.5+1, which enforces proper key verification. Alternatively, applications can implement a workaround by rejecting tokens containing a jwk header unless the key matches one in the trusted key store. The vulnerability has a CVSS v3.1 base score of 7.5, indicating high severity due to network attack vector, no privileges or user interaction required, and a significant impact on integrity. No public exploits have been reported to date, but the potential for abuse is high given the critical role of JWTs in authentication systems.
Potential Impact
This vulnerability can have severe consequences for organizations worldwide that use the affected versions of the appsup-dart jose library for JWT/JWS verification. Successful exploitation allows attackers to forge valid tokens, effectively bypassing authentication and authorization controls. This can lead to unauthorized access to sensitive systems, data breaches, privilege escalation, and potential lateral movement within networks. Applications relying on JWTs for session management, API authentication, or identity assertions are particularly at risk. The integrity of the authentication process is compromised, undermining trust in security controls and potentially exposing confidential information or critical resources. Given the widespread use of JWTs in modern web and mobile applications, the impact could be broad, affecting industries such as finance, healthcare, government, and technology. Although no known exploits are currently reported in the wild, the vulnerability's ease of exploitation and high impact make it a significant threat that demands immediate attention.
Mitigation Recommendations
To mitigate this vulnerability, organizations should prioritize upgrading the appsup-dart jose library to version 0.3.5+1 or later, where the issue is patched. If immediate upgrade is not feasible, implement a strict validation policy that rejects any JWT/JWS tokens containing a jwk header unless the embedded key matches a key already present in the application's trusted key store. Additionally, review and audit all token verification logic to ensure that only trusted keys are used for signature validation. Employ defense-in-depth strategies such as monitoring authentication logs for anomalous token usage patterns and implementing rate limiting to reduce the risk of automated exploitation attempts. Educate developers and security teams about the risks of accepting untrusted keys from token headers and enforce secure coding practices around cryptographic operations. Finally, maintain an inventory of all applications and services using the vulnerable library to ensure comprehensive remediation.
Affected Countries
United States, Germany, United Kingdom, France, Canada, Australia, Japan, South Korea, India, Brazil, Netherlands, Sweden
CVE-2026-34240: CWE-347: Improper Verification of Cryptographic Signature in appsup-dart jose
Description
JOSE is a Javascript Object Signing and Encryption (JOSE) library. Prior to version 0.3.5+1, a vulnerability in jose could allow an unauthenticated, remote attacker to forge valid JWS/JWT tokens by using a key embedded in the JOSE header (jwk). The vulnerability exists because key selection could treat header-provided jwk as a verification candidate even when that key was not present in the trusted key store. Since JOSE headers are untrusted input, an attacker could exploit this by creating a token payload, embedding an attacker-controlled public key in the header, and signing with the matching private key. Applications using affected versions for token verification are impacted. This issue has been patched in version 0.3.5+1. A workaround for this issue involves rejecting tokens where header jwk is present unless that jwk matches a key already present in the application's trusted key store.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability identified as CVE-2026-34240 affects the appsup-dart jose library, a JavaScript Object Signing and Encryption (JOSE) implementation used for handling JSON Web Tokens (JWT) and JSON Web Signatures (JWS). Prior to version 0.3.5+1, the library improperly verifies cryptographic signatures by accepting a public key embedded within the JOSE header (jwk) as a valid verification key without confirming it against a trusted key store. Since JOSE headers are untrusted input, an attacker can craft a malicious token by embedding a public key they control in the header and signing the token with the corresponding private key. The library then erroneously accepts this token as valid, enabling token forgery. This flaw corresponds to CWE-347 (Improper Verification of Cryptographic Signature). The vulnerability allows unauthenticated remote attackers to bypass authentication and authorization mechanisms in applications that rely on this library for token validation. The issue is resolved by upgrading to version 0.3.5+1, which enforces proper key verification. Alternatively, applications can implement a workaround by rejecting tokens containing a jwk header unless the key matches one in the trusted key store. The vulnerability has a CVSS v3.1 base score of 7.5, indicating high severity due to network attack vector, no privileges or user interaction required, and a significant impact on integrity. No public exploits have been reported to date, but the potential for abuse is high given the critical role of JWTs in authentication systems.
Potential Impact
This vulnerability can have severe consequences for organizations worldwide that use the affected versions of the appsup-dart jose library for JWT/JWS verification. Successful exploitation allows attackers to forge valid tokens, effectively bypassing authentication and authorization controls. This can lead to unauthorized access to sensitive systems, data breaches, privilege escalation, and potential lateral movement within networks. Applications relying on JWTs for session management, API authentication, or identity assertions are particularly at risk. The integrity of the authentication process is compromised, undermining trust in security controls and potentially exposing confidential information or critical resources. Given the widespread use of JWTs in modern web and mobile applications, the impact could be broad, affecting industries such as finance, healthcare, government, and technology. Although no known exploits are currently reported in the wild, the vulnerability's ease of exploitation and high impact make it a significant threat that demands immediate attention.
Mitigation Recommendations
To mitigate this vulnerability, organizations should prioritize upgrading the appsup-dart jose library to version 0.3.5+1 or later, where the issue is patched. If immediate upgrade is not feasible, implement a strict validation policy that rejects any JWT/JWS tokens containing a jwk header unless the embedded key matches a key already present in the application's trusted key store. Additionally, review and audit all token verification logic to ensure that only trusted keys are used for signature validation. Employ defense-in-depth strategies such as monitoring authentication logs for anomalous token usage patterns and implementing rate limiting to reduce the risk of automated exploitation attempts. Educate developers and security teams about the risks of accepting untrusted keys from token headers and enforce secure coding practices around cryptographic operations. Finally, maintain an inventory of all applications and services using the vulnerable library to ensure comprehensive remediation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-26T16:22:29.034Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69cbedf2e6bfc5ba1d248106
Added to database: 3/31/2026, 3:53:22 PM
Last enriched: 3/31/2026, 4:09:04 PM
Last updated: 4/1/2026, 6:20:25 AM
Views: 8
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.