Gemstash caches and serves unvalidated dependency data from an upstream
Published: November 19, 2026
SECURITY IDENTIFIERS
- GHSA: GHSA-xg28-cqw2-pggq
- Vendor Advisory: https://github.com/rubygems/gemstash/security/advisories/GHSA-xg28-cqw2-pggq
GEM
LIBRARY
PATCHED VERSIONS
>= 2.9.0
DESCRIPTION
Summary
The dependency data Gemstash fetches from an upstream with /api/v1/dependencies.json is cached and handed to clients, as JSON or as a Marshal dump Gemstash builds. It was cached and passed on as it came: entries of any shape, with any extra fields, and entries for gems that were never requested were all accepted and cached.
Impact
Limited: the cache is kept per gem source, so only clients using that same source see the data, and JSON cannot produce Ruby objects. It still lets an upstream plant arbitrary structures and unrequested gems into the Gemstash cache and into what its clients deserialize.
