Re:A GitHub Issue Title Compromised 4k Developer Machines
by gfody on Thursday March 05, 2026 @03:09PM
(#47266629)
yikes.. there should be the cli equivalent of that warning banner at the very least. combine this with something like gitc0ffee and it's downright dangerous
Re:A GitHub Issue Title Compromised 4k Developer Machines
by WorldMaker on Friday March 06, 2026 @11:25AM
(#47277044)
A YAML linter for it, too. I was appreciating the cron input overlay in the current GitHub Actions VS Code extension. In ghost text beside a cron: 'something' input it gives you a human-readable description. Seems like it could also do a similar thing for actions commit refs, show a simple verification if it corresponds to a tag or not in that repo.
Re:A GitHub Issue Title Compromised 4k Developer Machines
by tomjakubowski on Thursday March 05, 2026 @04:38PM
(#47267671)
> But this commit doesn't even have to belong to the preceding repository. You can reference a commit on a fork. Great way to sneak in an xz-utils style backdoor into critical CI workflows.
Wow. Does the SHA need to belong to a fork of the repo? Or is GitHub just exposing all (public?) repo commits as a giant content-addressable store?
Re:A GitHub Issue Title Compromised 4k Developer Machines
by sheept on Thursday March 05, 2026 @04:48PM
(#47267769)
Needs to be a fork.
Related: https://trufflesecurity.com/blog/anyone-can-access-deleted-a...
Re:A GitHub Issue Title Compromised 4k Developer Machines
by PunchyHamster on Friday March 06, 2026 @03:53AM
(#47272622)
It appears that under their system all forks belong to same repo (I imagine they just make _fork/<forkname> ref under git when there is something forked off main repo) presumably to save on storage. And so accessing a single commit doesn't really care about origin(as finding to which branch(es) commit belongs would be a lot of work)
There's another way it can be exploited. It's very common to pin Actions in workflows these days by their commit hash like this:
But this commit doesn't even have to belong to the preceding repository. You can reference a commit on a fork. Great way to sneak in an xz-utils style backdoor into critical CI workflows.GitHub just doesn't care about security. Actions is a security disaster and has been for over a decade. They would rather spend years migrating to Azure for no reason and have multiple outages a week than do anything anybody cares about.