Why do they need to stir up needless fear by using words like "BREAKING", "unauthorized access", or "millions of repositories" about the vulnerability that they caught before it was exploited in their X.com? https://x.com/wiz_io/status/2049153209982140718
GitHub RCE Vulnerability: CVE-2026-3854 Breakdown
81–90 of 97 posts
Re: GitHub RCE Vulnerability: CVE-2026-3854 Breakdown
#82They hint at their AI-augmented reversing methodology, which demonstrates one of the core strengths of current LLM agents. These models, trained extensively on code, can immensely speed up the process of understanding complex system internals. Security research historically has two difficult components that build on one another: 1. Understanding complex system internals: uncovering the inner workings hidden by abstra…
But recently this signal got somewhat scrambled, or being sabotage by c++ fan boys (those coding AIs would help getting rid of dev/vendor lock-ing using c++ syntax complexity)
Re: GitHub RCE Vulnerability: CVE-2026-3854 Breakdown
#83Earlier quoted context omitted.
Pretty sure GitHub Enterprise Cloud is just Github hosting their enterprise server for you on Azure so you don't have to do the patching yourself.
Github enterprise cloud is on github.com and with more features: http://github.com/account/enterprises/new They don't host github enterprise server for you (though gitlab has something called gitlab dedicated which they host gitlab ee for you).
Perhaps this header mentioned in the article is related, maybe that's the toggle for the enterprise mode? Seems there is at least traces of "enterprise mode" on the normal github servers.
Re: GitHub RCE Vulnerability: CVE-2026-3854 Breakdown
#84Anyone 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.
Re: GitHub RCE Vulnerability: CVE-2026-3854 Breakdown
#85People keep wanting to replace GitHub, but with what? If GH is getting RCE's this late in the game who wants to take the chance something else won't?
Re: GitHub RCE Vulnerability: CVE-2026-3854 Breakdown
#86I know it's easy to say after the fact but still, wtf
Re: GitHub RCE Vulnerability: CVE-2026-3854 Breakdown
#87Earlier quoted context omitted.
Github enterprise cloud is on github.com and with more features: http://github.com/account/enterprises/new They don't host github enterprise server for you (though gitlab has something called gitlab dedicated which they host gitlab ee for you).
> X-Stat header that controls whether the server operates in enterprise mode. Perhaps this header mentioned in the article is related, maybe that's the toggle for the enterprise mode? Seems there is at least traces of "enterprise mode" on the normal github servers.
Re: GitHub RCE Vulnerability: CVE-2026-3854 Breakdown
#88Anyone 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.
Lots of Unit 8200 peeps.
"Trusted by more than 50% of Fortune 100 companies".
You choose to give your most precious data and the keys of infrastructure whose job was to steal information and with people that are still NSA/8200 employees.
Don't be surprised if one day they are compelled to share data or find dirt on people (they protect one well known LLM company).
It doesn't mean they are doing it, but clearly the incentive for it exists, + you are exposed to both US and IL jurisdictions risk.
Re: GitHub RCE Vulnerability: CVE-2026-3854 Breakdown
#89Earlier quoted context omitted.
Ah, you assumed I meant SaaS GitLab. I meant the self-hosted version. I would never host our source code on a remote service.
Why not?
And on equal footing, I trust our security more than theirs. Case in point.
Re: GitHub RCE Vulnerability: CVE-2026-3854 Breakdown
#90Another tour de force from Wiz, and a watershed moment in AI tooling enabling RE and compromise discovery.
It throws a wrench into the argument of not publishing your source because AI will more easily compromise the code. Another data point against doing security through obscurity.