CVE-2026-75509: joserfc claim-validation bypass via array-typed single-string claims (iss/sub/jti)

Published Aug 24, 2026
·
Updated

joserfc is a Python library that provides an implementation of several JSON Object Signing and Encryption (JOSE) standards. Prior to version 1.7.3, JWTClaimsRegistry applies membership matching to list-valued iss and sub claims, allowing an array-valued iss that contains the expected issuer to pass an intended equality check and enabling issuer-validation bypass. This issue is fixed in version 1.7.3.

Affected Software

1 affected component
pypi/joserfc<1.7.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade joserfc to a version that resolves this vulnerability.

    Fixed in 1.7.3

Event History

Aug 24, 2026
CVE Published
via MITRE·08:08 PM
Data Sourced
via MITRE·08:08 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are affected?

Deployments using the PyPI joserfc package prior to version 1.7.3 are affected when JWTClaimsRegistry validates issuer or subject claims as intended single-string equality checks.

2

What does an attacker need to exploit this issue?

An attacker needs to provide a JWT with an array-valued iss or sub claim that includes the expected value. The affected validation applies membership matching to list-valued claims rather than enforcing the intended equality check.

3

Is a default configuration known to be affected?

The available information does not identify a default configuration. Exposure depends on use of JWTClaimsRegistry for issuer or subject claim validation.

4

What is the remediation?

Upgrade joserfc to version 1.7.3, which fixes the claim-validation behavior.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203