Allow excon 1.x to address CVE-2026-54171 (GHSA-48rx-c7pg-q66r)#87
Open
jagdeepsingh wants to merge 1 commit into
Open
Allow excon 1.x to address CVE-2026-54171 (GHSA-48rx-c7pg-q66r)#87jagdeepsingh wants to merge 1 commit into
jagdeepsingh wants to merge 1 commit into
Conversation
excon < 1.5.0 is affected by a redirect header-leak advisory (CVE-2026-54171), fixed in excon >= 1.5.0. The current `~> 0.20` constraint caps excon below 1.0, preventing downstream apps from upgrading to a patched release. This widens the ceiling to `< 2` while keeping the existing `>= 0.20` floor for backward compatibility. The client only uses stable excon APIs (Excon.new, Excon.get/post, Excon::Errors::SocketError, Excon::Response.new), all of which are present and unchanged in excon 1.x — verified against excon 1.2.3 — so no code changes are required.
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
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.
excon < 1.5.0 is affected by a redirect header-leak advisory (CVE-2026-54171), fixed in excon >= 1.5.0. The current
~> 0.20constraint caps excon below 1.0, preventing downstream apps from upgrading to a patched release.This widens the ceiling to
< 2while keeping the existing>= 0.20floor for backward compatibility. The client only uses stable excon APIs (Excon.new, Excon.get/post, Excon::Errors::SocketError, Excon::Response.new), all of which are present and unchanged in excon 1.x — verified against excon 1.2.3 — so no code changes are required.