The GitLab patch landed a week early. Alpine still got hit — because the real bug lived in Ruby, inside your container

Alpine Linux just published a post-mortem that should be required reading for anyone who runs GitLab and thinks a version number is a security policy. On October 20–21, an attacker used a freshly registered account to feed crafted CI configurations to Alpine's GitLab instance, aiming at CVE-2026-97229, a CVSS 10.0 remote code execution flaw in how GitLab evaluates regular expressions in CI config. The attacks crashed GitLab worker processes eight times. In four of them, the exploit got partway through and only failed at the next step. The attacker also downloaded Alpine's GitLab container image — likely to tune the exploit against that exact build.

Here's the part that stings: GitLab shipped the fix on October 12, a full week before the attack. Alpine had even upgraded to GitLab 19.3.6 on October 22. And the instance was still exploitable anyway. The reason is that the actual bug isn't in GitLab's own code — it's in Onigmo, the regex engine built into Ruby, which GitLab bundles inside its packages and container images. GitLab's October patch carried the Ruby fix, but Alpine's custom-built image didn't inherit it. The hole stayed open until Ruby itself shipped 3.3.13 on October 23 and Alpine rebuilt the image around it. Your vulnerability surface isn't the app version you typed into the upgrade ticket — it's the pile of dependencies the vendor baked into the artifact, some of which you can't see, let alone patch directly.

What Alpine did next is the other lesson. The logs needed to prove or disprove code execution were missing, along with any record of outbound connections. Rather than argue about probabilities, the team treated the instance as compromised: full rebuild from scratch, all passwords reset, and a public reminder that people who reused their GitLab password elsewhere should change it there too — because attackers were already trying leaked credentials from other breaches against the account base. That's a defensible posture, but it's also expensive for a volunteer-run project, and it lands on every team that self-hosts: incident response without logging is just rebuild-or-guess. If you self-host anything, the audit question writes itself: can you name the regex engine, JSON parser, or HTTP client your CI platform ships inside its container image? Most admins can't, and can't patch them independently even when they can. The good news Alpine verified is that aports, the packages, and the October 21 releases were untouched — the supply chain held this time. But an attacker already downloading your exact container image to tune an exploit against your specific build is not a hypothetical you should count on failing twice.

Source article image
Source image 1

Sources

Comments

Post a Comment

Popular posts from this blog

AI Is Starting to Feel Less Like a Gadget and More Like Infrastructure

Image
Modern AI doesn't replace infrastructure — it runs on top of it. (Photo: Unsplash) For a while, AI coverage had the energy of a mall demo kiosk: very shiny, slightly chaotic, and usually one prompt away from embarrassment. Lately, though, the more interesting story is less about flashy demos and more about infrastructure. A useful CNBC piece argued that AI is not simply going to vaporize enterprise software overnight, and that sounds about right. In real companies, software does not disappear just because a model can summarize a meeting or write a decent SQL query. What actually happens is messier and more practical: AI starts sneaking into the plumbing. It shows up in search, support workflows, procurement tools, analytics dashboards, and data pipelines. The real winners may not be the loudest chatbot wrappers, but the vendors that make enterprise systems easier to operate, easier to query, and slightly less soul-crushing for the humans trapped inside them. That is less cinematic ...
Read more

When Two AI Bots Finally Learned to Talk in Discord

I spent part of the day doing something that sounds like the setup for a bad joke: getting two local AI assistants to talk to each other in the same Discord channel. Not through a web UI. Not by bouncing prompts manually between windows like a human message queue. In the actual shared channel, where both could see the conversation and react to each other. The funny part is that the problem was not intelligence. It was manners. Both bots were defensive by default around bot-authored messages, which is the sensible setting if you do not want your infrastructure turning into a recursive support group. The downside is obvious: if both assistants treat other bots as suspicious background noise, they will never coordinate on anything more useful than silence. The fix was to make both sides accept bot-authored messages only when they were explicitly mentioned. That detail matters more than it sounds. Blanket bot acceptance is how you end up with two enthusiastic systems discovering each oth...
Read more

2.9 Billion Commits a Month, and Nobody Asked Who Checks Them

Image
GitHub's CTO has posted a postmortem that admits something a hyperscaler rarely says out loud: the growth explains it. On August 17, GitHub was down for seven hours and forty-seven minutes — not because of a bad deploy or a bad config change, but because traffic hit a new peak and a critical component in its Central US data center failed to scale with it. Recovery was made uglier by a client-side retry loop that kept hammering the platform while it came back up, which is a nice picture of what happens when a lot of automated clients retry without backoff. The number sitting behind all of it is the interesting one: monthly commits went from 1.4 billion to 2.9 billion in four months. For years, the commit curve tracked the developer population almost one-to-one. It just stopped. GitHub's own postmortem frames it as a capacity story — 3 million added CPU cores, 120 petabytes of storage, Azure now serving 58% of platform load up from 12% in May — and for GitHub, that is fixable wit...
Read more