Authentication Bypass Affecting joserfc package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.12% (2nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ECHOLATEST-JOSERFC-21184725
  • published18 Oct 2026
  • disclosed15 Oct 2026

Introduced: 15 Oct 2026

NewCVE-2026-102946  (opens in a new tab)
CWE-290  (opens in a new tab)
CWE-345  (opens in a new tab)
CWE-347  (opens in a new tab)

How to fix?

There is no fixed version for Echo:latest joserfc.

NVD Description

Note: Versions mentioned in the description apply only to the upstream joserfc package and not the joserfc package as distributed by Echo. See How to fix? for Echo:latest relevant fixed versions and status.

joserfc is a Python library that provides an implementation of several JSON Object Signing and Encryption (JOSE) standards. Prior to 1.7.4, joserfc.jws.deserialize_json() accepts a JWS General JSON Serialization with an empty signatures array as authenticated. The verify_general_json() loop performs no iterations for the empty array and returns success because no signature check failed, allowing an attacker without a signing key to supply an arbitrary payload that relying applications may treat as authentic. The issue affects the General JSON Serialization path; compact JWS and JWT decoding, Flattened JSON serialization, and JWE JSON processing do not follow this vulnerable path. This issue is fixed in version 1.7.4.

CVSS Base Scores

version 3.1