exploit · Fri 24 Jul 2026 · 21:14 UTC
RT by @cyb3rops: We successfully achieved an RCE on GitLab in its default configuration. Historically, most GitLab RCEs have lived in the web or application-logic layers. This time, guided by the @depthfirstlabs spirit, we went deeper: into the low-level gem dependency chain beneath GitLab. The result? By sending crafted JSON data, we could exploit memory-corruption vulnerabilities buried deep in that chain and take control of the GitLab application server. @depthfirstlabs brings together some of the smartest people, and is building the best security AI agent. Follow our work, and come join us! Read more about this in the comment...
Filed UTCSource X ↗
<p>We successfully achieved an RCE on GitLab in its default configuration.<br /> Historically, most GitLab RCEs have lived in the web or application-logic layers. This time, guided by the <a href="https://nitter.net/depthfirstlabs" title="depthfirst">@depthfirstlabs</a> spirit, we went deeper: into the low-level gem dependency chain beneath GitLab.<br /> The result? …
Get the next one first.
Every dispatch goes to Telegram and RSS the moment it is published, and the whole wire is a keyless JSON API.
Check your stack
Paste what you run: the CVEs exploited in the wild against it, and who is cited as exploiting them, with the report.
Stack checkNo key. No signup.