github.com/lestrrat-go/jwx vulnerable to Potential Padding Oracle Attack

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary Decrypting AES-CBC encrypted JWE has Potential Padding Oracle Attack Vulnerability. Details On v2.0.10, decrypting AES-CBC encrypted JWE may return an error "failed to generate plaintext from decrypted blocks: invalid padding": https://github.com/lestrrat-go/jwx/blob/8840ffd4afc5839f591ff0e9ba9034af52b1643e/jwe/internal/aescbc/aescbc.go#L210-L213 Reporting padding error causes Padding Oracle Attack Vulnerability. RFC 7516 JSON Web Encryption (JWE) says that we MUST NOT do this. 11.5. Timing Attacks To mitigate the attacks described in RFC 3218 [RFC3218], the recipient MUST NOT distinguish between format, padding, and length errors of encrypted keys. It is strongly recommended, in the event of receiving an improperly formatted key, that the recipient substitute a randomly generated CEK and proceed to the next step, to mitigate timing attacks. In addition, the time to remove padding depends on the length of the padding. It may leak the length of the padding by Timing Attacks.…

Published by the source

14 Jun 2023, 17:24 UTC

Last modified by the source

14 Jun 2023, 17:24 UTC

Source last checked

26 Oct 2026, 14:58 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-rm8v-mxj3-5rmq

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-rm8v-mxj3-5rmq

Advisory: github.com/lestrrat-go/jwx vulnerable to Potential Padding Oracle Attack
IDs: GHSA-rm8v-mxj3-5rmq
Record: https://patchnext.com/advisories/ghsa-rm8v-mxj3-5rmq (revision 1, source checked 26 Oct 2026, 14:58 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/lestrrat-go/jwx/v2 2.0.11; github.com/lestrrat-go/jwx 1.2.26. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/lestrrat-go/jwx/v2: affected <= 2.0.10; fixed in 2.0.11
- Go github.com/lestrrat-go/jwx: affected <= 1.2.25; fixed in 1.2.26

## Suggested inspection (read-only)
- Go github.com/lestrrat-go/jwx/v2: check the installed version with your package manager.
- Go github.com/lestrrat-go/jwx: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/lestrrat-go/jwx/v2, github.com/lestrrat-go/jwx.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-rm8v-mxj3-5rmq (GitHub-reviewed advisory GHSA-rm8v-mxj3-5rmq lists affected ranges: Go github.com/lestrrat-go/jwx/v2 >=0 =0 <=1.2.25)

Commands are suggestions: review each one before running it.