[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f0blMMKkI3RfY0R3xOuv8IMEGqZE7jjms56WDcmTu0eo":3},{"lesson":4},{"id":5,"slug":6,"article_id":7,"title":8,"body":9,"prevention":10,"framework_refs":11,"framework_notes":19,"status":27,"created_at":28,"published_at":29,"article":30,"tags":34,"podcasts":47,"controls":54},"2acaf4cc-e06d-40b3-ae11-a14be4d4ff9e","github-actions-pwn-request-attacks-still-viable-despite-2026-hardening","55f9f598-95a5-4a66-93b9-4f8f5b2ade1c","GitHub Actions 'Pwn Request' Attacks Still Viable Despite 2026 Hardening","Despite GitHub's significant security improvements to the Actions platform in 2026, attackers can still exploit residual weaknesses in CI\u002FCD pipelines — particularly through explicit opt-ins to `pull_request_target`, outdated checkout action versions, unprotected workflow triggers, and script injection vulnerabilities. The core problem is that security defaults only protect repositories that haven't been manually configured to bypass them, leaving organizations that customized their workflows before the hardening changes especially exposed. This matters because a successful 'pwn request' attack allows an untrusted fork contributor to execute arbitrary code in the context of the target repository, potentially exfiltrating secrets, poisoning build artifacts, or compromising downstream supply chain dependencies. Misconfigured CI\u002FCD pipelines represent a high-value, often overlooked attack surface that bridges code repositories and production environments.","**Immediate actions:**\n- Audit all workflows using `pull_request_target` and remove or restrict the trigger unless explicitly required, applying least-privilege permissions.\n- Pin all GitHub Actions to a specific full-length commit SHA from a trusted, recent commit — not a mutable tag — and verify these SHAs are current post-2026 hardening changes.\n- Scan all workflow YAML files for script injection sinks (e.g., `${{ github.event.pull_request.title }}` interpolated into `run:` steps) and sanitize or eliminate them immediately.\n\n**Long-term improvements:**\n- Implement a CI\u002FCD security policy that mandates peer review of any workflow changes, treating `.github\u002Fworkflows\u002F` files as security-critical infrastructure.\n- Adopt a secrets management solution that scopes repository secrets to protected branches only, and rotate any secrets potentially exposed to fork-based workflows.\n- Establish a recurring (quarterly) automated review of all workflow configurations against a hardened baseline, flagging deviations for remediation.\n\n**Detection measures:**\n- Enable GitHub's audit log streaming and alert on any workflow runs triggered by external fork pull requests that access secrets or sensitive cache tokens.\n- Integrate a static analysis tool (e.g., Semgrep, Zizmor) into the repository's own CI pipeline to continuously detect insecure workflow patterns before they reach the main branch.",[12,13,14,15,16,17,18],"CIS Control 7: Continuous Vulnerability Management","NIST SP 800-53 SI-2: Flaw Remediation","NIST CSF 2.0 PR.AA: Identity Management, Authentication, and Access Control","ISO\u002FIEC 27001:2022 A.8.8: Management of technical vulnerabilities","OWASP A06:2021 Vulnerable and Outdated Components","MITRE ATT&CK T1566: Phishing","NIS2 Article 21(2)(b)",{"NIS2 Article 21(2)(b)":20,"MITRE ATT&CK T1566: Phishing":21,"NIST SP 800-53 SI-2: Flaw Remediation":22,"OWASP A06:2021 Vulnerable and Outdated Components":23,"CIS Control 7: Continuous Vulnerability Management":24,"ISO\u002FIEC 27001:2022 A.8.8: Management of technical vulnerabilities":25,"NIST CSF 2.0 PR.AA: Identity Management, Authentication, and Access Control":26},"NIS2 requires entities to implement controls covering incident handling and security in network and information systems, including securing development pipelines that, if compromised, could result in supply chain incidents affecting downstream users.","While not phishing in the email sense, the 'pwn request' attack pattern mirrors the same initial-access social engineering mechanic — a malicious contributor submits a seemingly legitimate pull request to trigger privileged workflow execution, exploiting developer trust.","SI-2 requires organizations to identify, report, and correct information system flaws; keeping GitHub Actions pinned to post-hardening commit SHAs and updating outdated checkout versions is a direct flaw-remediation obligation.","Using outdated versions of the `actions\u002Fcheckout` action that predate GitHub's 2026 hardening changes is a textbook instance of relying on a vulnerable, outdated component in the software delivery pipeline.","Regularly assessing workflow configurations and action dependency versions against known-insecure patterns (such as outdated checkout versions) would surface exploitable conditions before attackers leverage them.","A.8.8 requires timely identification and remediation of technical vulnerabilities in software, which extends to CI\u002FCD pipeline components such as insecurely configured Actions triggers and stale action dependencies.","Restricting which workflow triggers can access repository secrets — ensuring only trusted, authorized code paths ever receive credentials — is precisely the access control posture PR.AA demands.","published","2026-10-26T14:21:48.759733+00:00","2026-10-26T14:21:48.744+00:00",{"id":7,"url":31,"slug":32,"title":33},"https:\u002F\u002Fwww.wiz.io\u002Fblog\u002Fgithub-actions-security-pwn-request-reckoning","the-pwn-request-reckoning-what-still-works-against-github-actions-94220a","The Pwn Request Reckoning: What Still Works Against GitHub Actions",[35,41],{"id":36,"name":37,"slug":38,"description":39,"color":40},"1ec88fde-2d0f-4ed8-932a-33f5ccc0fdc7","Access Control","access-control","Excessive privileges, missing MFA, weak auth","#f97316",{"id":42,"name":43,"slug":44,"description":45,"color":46},"859cf0ad-a7e9-42bb-a75d-bac6511fa5d5","Configuration Management","configuration-management","Misconfigs, default credentials, exposed services","#eab308",[48],{"id":49,"date":50,"edition":51,"title":52,"audio_url":53},"6d211e7d-c835-4a7b-965d-11a96685f5fd","2026-10-26","afternoon","ThreatNoir Afternoon Brief — October 26","https:\u002F\u002Fcdn.threatnoir.com\u002Fpodcasts\u002F2026-10-26\u002Fthreatnoir-afternoon-brief-2026-10-26.mp3",[55,59,63],{"slug":56,"name":57,"problem":58},"breach-attack-simulation","Breach and attack simulation","You only find out whether your security tools stop an attack when a real attacker tries.",{"slug":60,"name":61,"problem":62},"endpoint-detection-response","Endpoint detection and response (EDR and XDR)","Malware and hands-on-keyboard attackers on laptops and servers get spotted and stopped.",{"slug":64,"name":65,"problem":66},"security-awareness-training","Security awareness training and phishing simulation","People recognise and report attacks instead of falling for them."]