buildOne report1 publisher Once a workflow has an actions.lock entry, a moved tag no longer changes what GitHub Actions runs
GitHub's Actions lockfile, in public preview since October 2026, pins each action in a workflow to a commit SHA, DEV Community reports. A pinned commit that vanishes fails the run, so teams trade silent drift for hard errors.
Reality
- Evidence30
- Adoption
- Not scored
- Hype gap+20
- Incentives
- Not scored
- Confidence35
buildOne report1 publisher Scanner authors find six exploitable GitHub workflows among 60 that use pull_request_target
Scanner authors writing on dev.to hand-checked 60 public pull_request_target workflows and judged 6 exploitable by anyone who can open a pull request. About as many looked dangerous and were safe, so an audit has to read what runs after the checkout.
Reality
- Evidence40
- Adoption
- Not scored
- Hype gap+5
- Incentives60
- Confidence40
buildOne report1 publisher One API call decides whether your SHA pin still means what it says
SHA pinning drew a clean line through the tj-actions compromise, and then Dependabot began bumping hashes faster than anyone could read them. The claim worth enforcing is the version comment that nothing verifies.
Reality
- Evidence62
- Adoption
- Not scored
- Hype gap+15
- Incentives40
- Confidence58
buildOne report1 publisher A single rule produced 59 of 61 medium findings before its author read GitHub's docs
A cybersecurity undergraduate's taint scanner for GitHub Actions returned 61 medium-severity findings across 67 repositories. Of those, 59 came from one rule he then found was wrong about how the platform works.
Reality
- Evidence58
- Adoption
- Not scored
- Hype gap−25
- Incentives35
- Confidence55
Microsoft maps stale DNS and commit rights into one cloud web app attack surface
The new cloud web applications threat matrix sorts eleven ATT&CK tactics for managed runtimes and serverless code, starting with assets an app team rarely owns, such as dead DNS records and linked source repositories.
Reality
- Evidence74
- Adoption
- Not scored
- Hype gap+6
- Incentives58
- Confidence67
buildOne report1 publisher TeamCity's new OIDC plugin turns your build server into the credential issuer
Build configurations can now authenticate to AWS and Google Cloud without stored keys, provided you accept that the TeamCity server holds the signing key and that rotating it leaves already-issued tokens valid.
Reality
- Evidence46
- Adoption12
- Hype gap+14
- Incentives82
- Confidence56
buildConfirmed2 publishers JetBrains says CVE-2026-63077 lets an unauthenticated attacker run arbitrary commands on a TeamCity server. The rotation list it handed Cadence users doubles as the recovery scope for anyone self-hosting.
Reality
- Evidence79
- Adoption71
- Hype gap−9
- Incentives73
- Confidence74
buildOne report1 publisher Checkout v7 warns and exits rather than clone fork code under pull_request_target
For anyone running pull_request_target, pinning v7 starts with a workflow audit rather than a version bump, and the credential relocation underneath it carries a runner version floor that self-hosted fleets should check first.
Reality
- Evidence30
- Adoption
- Not scored
- Hype gap+35
- Incentives55
- Confidence30
buildOne report1 publisher An eBPF egress filter for GitHub Actions that ships with no backend and states what it won't do
field-cage blocks outbound connections from Linux runners in the kernel, keeps its logs on the box, and disclaims step correlation, tamper detection and organization-wide visibility.
Reality
- Evidence34
- Adoption9
- Hype gap−12
- Incentives46
- Confidence36
CodeQL 2.26.3 treats workflow files as code, and cache poisoning as a finding you must triage
GitHub's August release retunes Actions queries for cache poisoning, output clobbering and untrusted checkouts. Most of the work went into cutting false positives, not adding coverage.
Reality
- Evidence58
- Adoption28
- Hype gap+6
- Incentives44
- Confidence60