Repository navigation
Vendor hex_core v0.20.1 - #1274
Merged
Merged
Conversation
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.
hex_core v0.20.1 fixes an infinite loop in the vendored
erl_tarwhen unpacking a GNU sparse file that ends in a hole to disk, and{error, badarg}for a sparse hole that crosses a 64 KiB boundary (GHSA-phm5-m6cj-5382, CVE-2026-96596). It also percent-encodes the values hex_core puts in API and repository URLs (hexpm/hex_core#239).v2.5.3 shipped this on the v2.5 branch, and the vendored files here are identical to the ones in that release. The changelog entries come with the v2.5.3 section in hexpm/hex#1273, the same way the v2.5.2 fixes are only listed in their release section.