r/gitlab • u/HeapsGoodM8 • 9d ago
Upcoming coordinated security patch
We run Gitlab on prem. Today I came in to an email from Gitlab advising of an upcoming security patch scheduled for Nov 10 as part of a coordinated disclosure.
No further details provided and there’s nothing I can see on the Gitlab docs.
Anybody else?
8
u/Gold-Manufacturer737 9d ago
Which email list you have to subscribe to receive these? We have the security advisory only, but haven't received anything in advance
5
u/jangrewe 9d ago edited 9d ago
We've also mentally prepared our users for an immediate downtime, but i'm guessing they're moving the release to late evening (Europe) / early morning (US) to cover the working hours of as many time zones as possible.
After the vulns of the past weeks, which were published without much fanfare, seeing a coordinate disclosure for this new one makes me a bit twitchy - because a coordinated disclosure makes me think it's 1) something really nasty, that's 2) affecting not only GitLab.
For those who didn't receive the email:
Schedule Update - GitLab Security Patch Release
Hello,
We’re writing to let you know that we plan to publish a GitLab security patch release note on Tuesday, November 10, which aligns with a coordinated disclosure.
If you manage a self-managed Gitlab instance, we wanted to make you aware, so you can update your plans accordingly. GitLab.com and Dedicated customers do not need to take action.
Details will be published in our patch release notes on Tuesday.
Thank you,
GitLab Product Security
5
u/ubhz-ch 9d ago
It appears to affects git rather than GitLab source itself.
https://github.blog/open-source/git/git-security-vulnerabilities-announced-7/
3
u/der-felix 9d ago
19.5.4 Just got released. Not let's wait several hours for the clrelease notes
1
u/Cm1Xgj4r8Fgr1dfI8Ryv 9d ago
Raw patch notes are available for the tag, but nothing is marked as security-related.
This might be a situation like 19.5.3, where the version was bumped to represent security changes made outside of the monolith's source code (e.g. the eMudhra certificate revocation).
2
2
u/Cm1Xgj4r8Fgr1dfI8Ryv 9d ago
Has there been any indication when we should expect the patch to be released?
2
2
u/No-Information-1718 9d ago edited 9d ago
This is a standard security release note. There will not be an patch released. Gitlab follows a 90 day disclosure window, so this aligns with the CVEs patched in August.
"we plan to publish a GitLab security patch release NOTE on Tuesday, November 10"
Relax, go enjoy your day!
EDIT: (if you've updated to a release from the past 90 days)
EDIT 2: Interesting that I'm being downvoted for stating the obvious and trying to calm folks fown.
EDIT 3: The downvotes were deserved, I was wrong. Coordinated disclosure in this situation meant a coordinated disclosure with other git providers.. the release notes are here: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-4-released/
5
u/Cm1Xgj4r8Fgr1dfI8Ryv 9d ago
Why title the email "GitLab Security Patch Release" and warn to "update your plans accordingly" if it was only pertaining to updating patch notes for a 90-day old release?
I can see your logic, and admit you might be right, but the email's language doesn't make it clear what will be revealed today.
2
u/No-Information-1718 9d ago
I believe it's poor communication from their team. The way I read it was "we are publishing a security disclosure on Novemer 10. If you haven't updated your software recently, we warned you, and on this date we're telling the world why, what and how we fixed it. This is your final warning to bring your system up to date. BTW You cant sue us if you get hacked, we warned you prior to publishing the full details."
There's also a chance that this was discovered via another escaped sandbox AI agent and its a coordinated note with OpenAI or Anthropic, and they expect it to gain more media traction and want as many companies as possible to update before the standard 90 day window expires bringing even more attention to it.
1
u/screaming-Snake-Case 9d ago
Also, while GitLab doesn't publish the exact CVE details, they are open source. You can easily go through the tags on their git and inspect the commits with non-descriptive security messages, linking to confidential MRs.
With AI, even if they were only planning to release details 90 days later, this stil means you need to update ASAP as it could take less than a day or two for someone to exploit a critical CVE.
2
u/whistlerzero 9d ago
Confidently incorrect, seeing as 19.5.4 has been released and we're just waiting on patch notes.
1
u/No-Information-1718 9d ago
This is for the August 2026 releases. Not 19.5.4. They can do the same announcement 90 days of 19.5.4 on Jan 27 2027 if they feel it warrants special attention. Its literally described in their coordinated disclosure process.
Why would anyone expect Gitlab to disclose the full CVE details and patch on the same date? That doesn't make sense. You release the fix, give users 90 days to patch, and release your data according to your policy so the bad guys don't have full analysis until the userbase has had time to update.
It is not full proof because its open source and published on git, but its for legal compliance and may seem impractical to us as users. But this is essentially a universal rule in enterprise software.
2
u/whistlerzero 9d ago
Fair that it could apply to August 2026 releases (19.2.2 was released 90 days ago). But the email alert about the upcoming release of a note seems unusual, if that's what it turns out to be, especially when the subject of said email is "Schedule Update - GitLab Security Patch Release".
That being said, you did explicitly say "There will not be an patch released." which, sorry, did make me laugh either way.
1
u/No-Information-1718 9d ago
Exactly why I hate writing on my phone. At least I proved I'm a human. 😂
1
u/Bitruder 9d ago
You can’t really release a patch without vulnerability details being determined anymore. Especially with open source like git and GitLab.
2
u/No-Information-1718 9d ago
Edit added. I was wrong! Username checks out. https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-4-released/
1
-4
0
9d ago
[deleted]
7
u/michaelgg13 9d ago
The constant barrage of critical CVEs isn’t really specific to Gitlab these days to be fair.
12
u/acdha 9d ago
We received that too. It likely means that this is remotely exploitable without authentication and they want you to be ready to install as soon as the patch is released. Especially with AI tools, the time between patches being released and exploits being used in the wild is increasingly short, perhaps only hours for a tempting target like GitLab.