Skip to content

[CVE] Updating Rack#367

Merged
johnmccrae merged 1 commit into
mainfrom
jfm/chef18-update-rack
May 27, 2026
Merged

[CVE] Updating Rack#367
johnmccrae merged 1 commit into
mainfrom
jfm/chef18-update-rack

Conversation

@johnmccrae
Copy link
Copy Markdown
Contributor

Description

Rack 3.2.5 has a CVE. Chef-Zero was vulnerable to all kinds of mayhem because the version constraint was too low. We're fixing that here.

Related Issue

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

  • I have read the CONTRIBUTING document.
  • I have run the pre-merge tests locally and they pass.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • If Gemfile.lock has changed, I have used --conservative to do it and included the full output in the Description above.
  • All new and existing tests passed.
  • All commits have been signed-off for the Developer Certificate of Origin.

Signed-off-by: John McCrae <john.mccrae@progress.com>
@johnmccrae johnmccrae requested review from a team and jaymzh as code owners May 26, 2026 22:09
@johnmccrae johnmccrae changed the title Updating Rack [CVE] Updating Rack May 27, 2026
@johnmccrae johnmccrae merged commit a15dd17 into main May 27, 2026
43 checks passed
@johnmccrae johnmccrae deleted the jfm/chef18-update-rack branch May 27, 2026 18:52
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.

2 participants