Posted in Security Operations
Most teams harden production. Very few treat their Git server as production. They should. This summer's…
Craig M. — Chief Product Officer @ Cyberr®
Most teams harden production. Very few treat their Git server as production.
They should.
This summer's Gitea flaw (CVE-2026-60004, CVSS 9.8) only needed write access to a repository to run shell commands on the server. With open self-registration, Gitea's default, that meant anyone: sign up, create a repo, own the host. CISA added it to its exploited list in August, and in one reported case the attack chain ran in about eleven seconds.
The payload was a crypto miner. The real prize was everything else on that box: source code, CI secrets, deploy keys.
Three checks worth doing this week:
→ Is self-registration off on every internal dev tool?
→ Does your Git service account have more access than it needs?
→ Would you notice a new hook file appearing in a repo?
Your developer tooling is part of your attack surface, not a step before it.
5 reactions · 1 comments
Comments
Schomer: Spot on, Craig. The Gitea CVSS 9.8 flaw exposes the core vulnerability of ambient trust inside internal dev clusters. Most architectures assume that once a session is authenticated via self-registration or write access, the underlying command payload is safe to parse. When an exploit chain executes in eleven seconds, waiting for reactive file-hook alerts or secret rotation is too late. The only wa