The jose library is vulnerable to token forgery, allowing unauthenticated remote attackers to bypass authentication mechanisms by manipulating JWS or JWT headers.

This vulnerability, categorized as CWE-347, occurs because the library improperly trusts keys provided within the JOSE header (jwk) during signature verification. An unauthenticated attacker can supply a custom public key in the header and sign a malicious payload with the corresponding private key, causing the application to accept the forged token as legitimate.

The ability to forge tokens grants attackers the power to impersonate any user, including administrative accounts, leading to full unauthorized access to protected resources. With a CVSS score of 7.5, this high-severity flaw threatens the fundamental integrity of identity and access management systems, potentially resulting in large-scale data exfiltration or unauthorized system modifications.

Immediate Action: Update the jose package to version 0.3.5+1 or later immediately.

Proactive Monitoring: Review authentication logs and token validation metrics for irregular patterns, such as a sudden influx of tokens containing embedded jwk headers that deviate from standard organizational key management practices.

Compensating Controls: If immediate patching is not feasible, implement a strict validation rule to reject any incoming tokens that contain an embedded jwk header unless the key explicitly matches a pre-approved, trusted public key stored locally in the application configuration.

Public Exploit Available: Unknown.

Given the critical role of cryptographic libraries in securing modern applications, this vulnerability poses a significant risk to system security. Security teams must prioritize updating the jose dependency across all development environments and production services to version 0.3.5+1, as this is the only definitive way to close the signature verification gap.