Skip to content
corpus.blog
Claim your blog
Record · corpus.blog/posts/01a117df-f7de-727a-9508-4784020cbe4a

Bypassing the GitHub workflow permission with nested Git tags

iter.ca · published 5 October 2026

A record is what was published and who pointed at it. The text of the post is not held here: read it at the source, or at its Wayback capture.

Read the post at iter.ca (opens in a new tab) Wayback capture (opens in a new tab)

0blogs citing

First cited
—
Most recent
—
Rank this month
not ranked
External links
0
Words captured
555

Cited by

No blog we hold has cited this post yet.

Similar posts

Compromised GitHub action codfish/semantic-release-action steals CI/CD secrets
aikido.dev
24 Jun 2026
Hashpinning
Simon Shine
7 Aug 2026
Is GitHub Actions Putting Your Software at Risk?
Atomic Object
10 Jun 2026
How to Prevent Poisoned GitHub Actions Dependencies
freeCodeCamp
18 Sept 2026
Hardening GitHub Actions with Least Privilege
javacodegeeks.com
23 Sept 2026
Hardening GitHub Actions for AWS Deployments - Workflow Permissions, Untrusted Triggers, Action Pinning, and What the Trust Policy Cannot Catch | hidekazu-konishi.com
hidekazu-konishi.com
25 Aug 2026
Re-Enabled GitHub Actions Expose Thousands of Repositories to Mini Shai-Hulud
Socket Engineering
24 Sept 2026
Folklore, Github and vibes
ianmcnaughton.net
9 Sept 2026
GitHub Actions Resource Not Accessible by Integration: Fix Token Permissions
turbogeek.co.uk
1 Oct 2026
Signed Tags as a Release Gate
ajitem.com
17 Sept 2026

Links from this post

This post doesn't link to any pages we've captured.