GitLab security incident: attempted exploitation of CVE-2026-97229
5 comments · linux, security
- Comments2
#2Rank now –
#2Peak rank
2Days on list
225Score · 7d
Oct 28, 2026First seen
Rank · 7 days
On Lobsters
linuxsecurity
- Score
- 23
- Comments
- 2
- Submitted by
- durrendal
- Tags
- linux, security
- Site
- alpinelinux.org
Story details from Lobsters ↗ · linked article on alpinelinux.org.
Trending history
GitLab security incident: attempted exploitation of CVE-2026-97229 was first seen on Lobsters · Hottest on Oct 28, 2026. Since then it has appeared in 23 checks on 2 different days. Its best position was #2 of 25, reached on Oct 29, 06:49 UTC. It is #2 right now, holding steady at #2 over the last 6 checks. The same link also trended on Hacker News, which raises its cross-platform score.
Rank history
Position on Lobsters · Hottest at every check (lower is better).
Last 14 days
Best rank per day (UTC).
13
2
Oct 16today
Metric history
▲ as reported by Lobsters.
Where it trended
| List | Best | Days | Checks | Last seen |
|---|---|---|---|---|
| Lobsters · Hottest | #2 | 2 | 23 | |
| YHacker News · Front page GitLab Security Incident: Attempted Exploitation of CVE-2026-97229 | same link | |||
From the discussion
A few top-level comments from Lobsters, shortened. Read the full thread on Lobsters.
> Upgrading to GitLab 19.3.6 on October 22 didn’t fix the vulnerability. The fix isn’t in GitLab’s own code but in a patch to Ruby, which GitLab applies only in its official packages. Our image used standard Ruby, so it didn’t get the patch. I guess this is a risk of repackaging things that I hadn't really considered…
It's exacerbated further by the fact that the patches to ruby didn't land until two days after Gitlab announced the CVE. But yes, if we had been using Gitlab's official images then we'd have gotten the fix regardless of where it was in the stack. It isn't Gitlab's or Ruby's fault though, just really unfortunate…
Questions
Is GitLab security incident: attempted exploitation of CVE-2026-97229 trending on Lobsters right now?
Yes. As of Oct 29, 10:19 UTC it is #2, holding steady at #2 over the last 6 checks.
What is the highest rank GitLab security incident: attempted exploitation of CVE-2026-97229 reached?
#2 on Lobsters · Hottest, on Oct 29, 06:49 UTC. Trendoday checks this list every 30 minutes.
How long has GitLab security incident: attempted exploitation of CVE-2026-97229 been trending?
It was first seen on Oct 28, 2026 and has been on the list on 2 days (23 checks) since.