fix: require unitsdb ~> 2.2.5 (CVE-2026-85396 rubyzip path traversal) - #76
Merged
Merged
Conversation
unitsdb 2.2.5 raises its rubyzip dependency to ~> 3.4, closing the path traversal vulnerability in rubyzip < 3.4.0 (CVE-2026-85396). Tighten the floor so fresh resolves cannot pick up the vulnerable unitsdb 2.2.4 / rubyzip 2.x chain.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Tightens the
unitsdbdependency floor from~> 2.2.4to~> 2.2.5so that fresh resolves of unitsml cannot pick up the chain affected by the rubyzip path traversal vulnerability (CVE-2026-85396):rubyzip ~> 3.4(vulnerability affects rubyzip < 3.4.0)~> 2.2.4still admitted unitsdb 2.2.4, which pinsrubyzip ~> 2.3Validated locally against unitsdb 2.2.5, lutaml-model 0.8.33, rubyzip 3.6.0: 456 examples, 0 failures; rubocop clean.
Testing
rubocop unitsml.gemspec: no offenses