Anyone in here work at Wiz? Seem like they do pretty good work. Tool itself has survived extreme growth/feature bloat and still does pretty well. Security team has found some really cool stuff.
> April 28, 2026<p>> GitHub Enterprise Server customers should upgrade immediately - at the time of this writing, our data indicates that 88% of instances are still vulnerable<p>> Upgrade to GHES version 3.19.3 or later<p><a href="https://docs.github.com/en/enterprise-server@3.19/admin/release-notes#3.19.3" rel="nofollow">https://docs.github.com/en/enterprise-server@3.19/admin/rele...</a> :<p>> Enterprise Server 3.19.3 - March 10, 2026<p>88% of on-prem customers haven't applied a critical security fix from 7 weeks ago, that seems ... bad.
I assume a fair amount of these on-prem customers restrict access to their GHES instance to be behind corporate VPN or something similar and are planning a date to upgrade their instance that won't affect operations.<p>Any public instance should update immediately though, it's not very hard to put together how to repro the vulnerability on your own from what they provide in the article and the fact that GitHub Enterprise source is publicly available.
If you're in the enterprise you can update something outside of the normal schedule and <i>guarantee</i> blow up everything (and be blamed) or you can stick with the schedule and hope for the best.<p>Guess which is usually picked ...
Question is how fragile the upgrade process is in large installations. In other enterprise software messing around with large amounts of data I've seen the smallest things break the install and leaving the OPs team rolling back. Was like SharePoint in the past, you were rolling a dice when upgrading it.
I was impressed enough by AI finding vulnerabilities in source code, but doing it in binary executables is just amazing. This has so much potential, good and bad.<p>And yet another lesson to not treat data as instructions. Sanitize all user input!
People keep wanting to replace GitHub, but with what?<p>If GH is getting RCE's this late in the game who wants to take the chance something else won't?
A "reasonable" answer is probably a primary self-hosted Forgejo instance as the canonical forge, while using GitHub as a mirror solely to take advantage of its free CI, while that lasts, while hosting secrets with a dedicated secret-hosting provider (I don't know what the provider du jour for this is these days).
> solely to take advantage of its free CI, while that lasts<p>Eh, if you want to be able to continue working, deploy and what not as normal during weekdays, I'd suggest also moving to Forgejo Actions if you're moving anyways. Not 100% compatible, but more or less the same, and even paying the same but with dedicated hardware you'd get way faster runners.
Replace a whole 24/7 team of devops people with myself?<p>As much as I'd like to believe that I'm worthy, I'm not.
If the primary forge's only job is to host the actual Git infrastructure (the code, the MRs, the issues, maybe a wiki), it's a lot more simple than GitHub, and probably more within the scope of what people can reasonably administer themselves.
I am personally now drawing a clear delineation between projects for my internal consumption (e.g. ansible scripts) and projects that have potential use for the general populace. For the prior, I now host a private Forgejo instance. For the latter, I'll put it on GitHub but mirror it to my Forgejo instance.<p>I was pleasantly shocked that Forgejo is literally a single binary with a relatively easy config. All my internal services reference my Forgejo instance so, if I need to bail on GitHub, it's low friction for me.
GitLab ?
The people who suggest gitlab, haven't used it. But I guess I could be tempted to try again...<p><a href="https://status.gitlab.com/pages/history/5b36dc6502d06804c08349f7" rel="nofollow">https://status.gitlab.com/pages/history/5b36dc6502d06804c083...</a>
.... git?<p>replace it with git.<p>if you want a whole ui you can use something like forgejo which has far fewer features likely leading to less issues.
GitHub case will be thought in schools how to screw up almost monopolistic position in the market in couple years. This is beyond bonkers.