CVE-2026-134459: PHP JWT Library: RSA1_5 (RSAES-PKCS1-v1_5) decryption lacks implicit rejection, exposing a Bleichenbacher/Marvin padding oracle

Published Nov 21, 2026
·
Updated

Impact

RSACrypt::decryptWithRSA15() (used by the RSA15 key-encryption algorithm) implements RSAES-PKCS1-v15 decryption by inspecting the padding after RSADP and throwing InvalidArgumentException as soon as the padding is malformed. It does not implement the implicit-rejection countermeasure required by RFC 3447 §7.2.2 / RFC 8017 §7.1.2 (return a deterministic pseudo-random value of the expected length on padding failure and let the downstream step fail uniformly).

From a JWE caller this yields a Bleichenbacher/Marvin padding oracle: an attacker submitting adaptively crafted encryptedkey values can distinguish (a) padding rejected, (b) padding valid but wrong CEK length, and (c) padding valid and full AEAD executed — even though JWEDecrypter returns the same false in all cases — because each path performs a measurably different amount of work, amplifiable by enlarging the ciphertext (CWE-208 timing side channel). Enough adaptive queries can recover the wrapped CEK.

Affected configurations

Applications that register RSA15 in their decryption AlgorithmManager and hold an RSA private key.

Patches

PKCS#1 v1.5 decryption now performs implicit rejection: on invalid padding (or unexpected recovered length) it returns a random CEK of the expected size selected in constant time, so the full content-decryption (AEAD) step always runs and fails uniformly, removing the observable difference between padding-valid and padding-invalid ciphertexts. Users are still strongly encouraged to migrate to RSA-OAEP.

Workarounds

Prefer RSA-OAEP/RSA-OAEP-256; do not enable RSA15 for untrusted tokens.

References

- RFC 3447 §7.2.2 / RFC 8017 §7.1.2 - Bleichenbacher (1998); Marvin attack - CWE-208: Observable Timing Discrepancy

Résolution

Un correctif a été préparé sur une branche dédiée basée sur 3.4.x, avec des tests anti-régression dédiés (fork privé temporaire de cette advisory, PR #1).

RSA15 — déchiffrement PKCS#1 v1.5 avec implicit rejection en temps constant (RFC 3447 §7.2.2) : un padding invalide n'est plus distinguable d'un padding valide, neutralisant l'oracle Bleichenbacher.

Validation : php -l OK, PHPUnit vert, aucune nouvelle erreur PHPStan introduite (différentiel nul vs 3.4.x), aucun commentaire ajouté dans le code source. Après merge, cascade prévue 3.4.x → 4.0.x → 4.1.x.

Other sources

web-token jwt-framework and jwt-library before 3.4.10, 4.0.x before 4.0.7, and 4.1.x before 4.1.7 contain a padding oracle in RSACrypt::decryptWithRSA15() because RSA15 decryption lacks implicit rejection, so invalid padding, wrong CEK length, and valid padding take measurably different time. Remote attackers can submit adaptively crafted JWE encryptedkey values and measure these timing differences to recover the wrapped content encryption key.

— MITRE

Affected Software

5 affected componentsFixes available
composer/web-token/jwt-framework<3.4.10, >=4.0.0<4.0.7, >=4.1.0<4.1.7
composer/web-token/jwt-library<3.4.10, >=4.0.0<4.0.7, >=4.1.0<4.1.7
composer/web-token/jwt-library<3.4.10
3.4.10
composer/web-token/jwt-library>=4.0.0<4.0.7
4.0.7
composer/web-token/jwt-library>=4.1.0<4.1.7
4.1.7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/web-token/jwt-library to a version that resolves this vulnerability.

    Fixed in 3.4.10
  2. Upgrade

    Upgrade composer/web-token/jwt-library to a version that resolves this vulnerability.

    Fixed in 4.0.7
  3. Upgrade

    Upgrade composer/web-token/jwt-library to a version that resolves this vulnerability.

    Fixed in 4.1.7
  4. Upgrade

    Upgrade web-token jwt-framework and jwt-library to a version that resolves this vulnerability.

    Fixed in 3.4.10
  5. Upgrade

    Upgrade web-token jwt-framework and jwt-library to a version that resolves this vulnerability.

    Fixed in 4.0.7
  6. Upgrade

    Upgrade web-token jwt-framework and jwt-library to a version that resolves this vulnerability.

    Fixed in 4.1.7
  7. Configuration

    Do not register RSA1_5 for untrusted tokens; prefer RSA-OAEP or RSA-OAEP-256.

    AlgorithmManager RSA1_5 = disabled

Event History

Jun 18, 2026
Advisory Published
via OSV·09:09 PM
Data Sourced
via OSV·09:09 PM
DescriptionSeverityWeaknessAffected Software
Nov 21, 2026
CVE Published
via MITRE·04:32 PM
Data Sourced
via MITRE·04:32 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:17 PM
DescriptionSeverityWeakness

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