Skip to content

Update rack, sinatra, and thin for security fixes - #578

Open
paulwfield wants to merge 1 commit into
sj26:mainfrom
paulwfield:fix/update-vulnerable-gem-dependencies
Open

Update rack, sinatra, and thin for security fixes#578
paulwfield wants to merge 1 commit into
sj26:mainfrom
paulwfield:fix/update-vulnerable-gem-dependencies

Conversation

@paulwfield

@paulwfield paulwfield commented Jun 16, 2026

Copy link
Copy Markdown

Summary

Updates mailcatcher runtime dependencies to patched releases that resolve HIGH/CRITICAL vulnerabilities reported by security scanners (e.g. Trivy):

  • rack ~> 3.2
  • sinatra ~> 4.2
  • thin ~> 2.0 (required for rack 3.x compatibility)

Motivation

mailcatcher 0.10.0 currently pins rack ~> 2.2, sinatra ~> 3.2, and thin ~> 1.8. These versions are flagged by vulnerability scanners for known CVEs in bundled dependencies. Bumping the declared dependencies allows consumers to install patched gem releases without post-install gemspec patching.

Test plan

  • gem build mailcatcher.gemspec && gem install ./mailcatcher-*.gem succeeds on ruby:3.3-alpine
  • mailcatcher --foreground starts and serves the web UI
  • Existing test suite passes in CI

Bump runtime dependencies to patched releases that resolve known
HIGH/CRITICAL vulnerabilities reported by security scanners:

- rack ~> 3.2 (CVE-2025-61770, CVE-2025-61771, CVE-2025-61772,
  CVE-2025-61919, CVE-2026-22860, CVE-2026-34785, CVE-2026-34827,
  CVE-2026-34829)
- sinatra ~> 4.2 (CVE-2025-61921)
- thin ~> 2.0 (rack 3.x compatibility)

@paulwfield paulwfield left a comment

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mailcatcher 0.10.0 currently pins rack ~> 2.2, sinatra ~> 3.2, and thin ~> 1.8. These versions are flagged by vulnerability scanners for known CVEs in bundled dependencies. Bumping the declared dependencies allows consumers to install patched gem releases without post-install gemspec patching.

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