Skip to content

Fix JWT CVE: upgrade jwt to 3.2.0 in oc-id and chef-server-ctl#4193

Merged
jashaik merged 1 commit into
mainfrom
shahid/fix-jwt-cve
May 21, 2026
Merged

Fix JWT CVE: upgrade jwt to 3.2.0 in oc-id and chef-server-ctl#4193
jashaik merged 1 commit into
mainfrom
shahid/fix-jwt-cve

Conversation

@jashaik
Copy link
Copy Markdown
Contributor

@jashaik jashaik commented May 21, 2026

jwt < 3.2.0 accepts attacker-forged tokens when an empty string key is used (empty-key HMAC bypass). JWT.decode with key '', nil, or a keyfinder returning '' would verify any signature via OpenSSL HMAC.

  • Pin jwt >= 3.2.0 in src/oc-id/Gemfile
  • Bump jwt 3.1.2 -> 3.2.0 in both Gemfile.lock files

Description

[Please describe what this change achieves]

Issues Resolved

[List any existing issues this PR resolves, or any Discourse or
StackOverflow discussions that are relevant]

Check List

jwt < 3.2.0 accepts attacker-forged tokens when an empty string key
is used (empty-key HMAC bypass). JWT.decode with key '', nil, or a
keyfinder returning '' would verify any signature via OpenSSL HMAC.

- Pin jwt >= 3.2.0 in src/oc-id/Gemfile
- Bump jwt 3.1.2 -> 3.2.0 in both Gemfile.lock files

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: Jan Shahid Shaik <jashaik@progress.com>
@jashaik jashaik requested review from a team as code owners May 21, 2026 14:16
@netlify
Copy link
Copy Markdown

netlify Bot commented May 21, 2026

👷 Deploy Preview for chef-server processing.

Name Link
🔨 Latest commit e63c74c
🔍 Latest deploy log https://app.netlify.com/projects/chef-server/deploys/6a0f13d1667534000811b7b6

@jashaik jashaik merged commit 02352f9 into main May 21, 2026
35 of 38 checks passed
@jashaik jashaik deleted the shahid/fix-jwt-cve branch May 21, 2026 14:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant