Skip to content

Allow excon 1.x to address CVE-2026-54171 (GHSA-48rx-c7pg-q66r)#87

Open
jagdeepsingh wants to merge 1 commit into
veritrans:masterfrom
jagdeepsingh:relax-excon-constraint-for-cve-2026-54171
Open

Allow excon 1.x to address CVE-2026-54171 (GHSA-48rx-c7pg-q66r)#87
jagdeepsingh wants to merge 1 commit into
veritrans:masterfrom
jagdeepsingh:relax-excon-constraint-for-cve-2026-54171

Conversation

@jagdeepsingh

Copy link
Copy Markdown

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.

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.
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