[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fP7JaeD6MIpM_bEo4QbEqb3_s4Xwby_5I9rhDdZ5eJHk":3},{"article":4,"iocs":49,"watch_terms":50,"solutions":51,"lesson":143},{"id":5,"title":6,"slug":7,"summary":8,"ai_summary":9,"brief":10,"url":11,"image_url":12,"published_at":13,"ingested_at":14,"relevance_score":15,"entities":16,"category_id":26,"category":27,"article_tags":31},"55f9f598-95a5-4a66-93b9-4f8f5b2ade1c","The Pwn Request Reckoning: What Still Works Against GitHub Actions","the-pwn-request-reckoning-what-still-works-against-github-actions-94220a","GitHub's 2026 Actions changes make pull_request_target attacks harder, but not impossible. Here's the residual attack surface and how to audit for it.","GitHub has implemented significant security changes to its Actions platform in 2026, particularly around the `pull_request_target` trigger, to mitigate risks associated with running workflows with repository secrets from untrusted forks. While default protections like checkout hardening and read-only cache tokens make exploitation harder, attackers can still find residual attack vectors. These include explicit opt-ins for `pull_request_target`, outdated checkout versions, unprotected triggers, and script injection, especially in private\u002Finternal repositories or when SHA pinning uses older commit SHAs that bypass newer protections.","GitHub Actions pull_request_target attacks persist despite 2026 security changes.","https:\u002F\u002Fwww.wiz.io\u002Fblog\u002Fgithub-actions-security-pwn-request-reckoning","https:\u002F\u002Fwww.datocms-assets.com\u002F75231\u002F1792497789-image.png","2026-10-26T13:24:12+00:00","2026-10-26T14:00:11.627308+00:00",8,[17,20,23],{"name":18,"type":19},"GitHub Actions","product",{"name":21,"type":22},"pull_request_target","technology",{"name":24,"type":25},"GitHub","vendor","26b0b636-0e31-4db1-bffb-61bdf9f20a58",{"id":26,"icon":28,"name":29,"slug":30},null,"Supply Chain","supply-chain",[32,37,39,44],{"category":33},{"id":34,"icon":28,"name":35,"slug":36},"02371804-cf6d-4449-98de-f1a2d4d9b266","Tools","tools",{"category":38},{"id":26,"icon":28,"name":29,"slug":30},{"category":40},{"id":41,"icon":28,"name":42,"slug":43},"80544778-fabb-4dcd-aa35-17492e5dcf4f","Vulnerabilities","vulnerabilities",{"category":45},{"id":46,"icon":28,"name":47,"slug":48},"e7b231c8-5f79-4465-8d38-1ef13aea5a14","Threat Intelligence","threat-intelligence",[],[24,18],{"controls":52,"vendors":137},[53,82,111],{"slug":54,"name":55,"problem":56,"products":57},"breach-attack-simulation","Breach and attack simulation","You only find out whether your security tools stop an attack when a real attacker tries.",[58,66,74],{"vendor_slug":59,"vendor_name":60,"vendor_logo":61,"product_slug":62,"product_name":63,"url":64,"description":65},"picus-security","Picus Security","\u002Fvendor-logos\u002Fpicus-security.png","picus-breach-and-attack-simulation","Picus Breach and Attack Simulation","https:\u002F\u002Fwww.picussecurity.com\u002Fplatform\u002Fbreach-and-attack-simulation","Continuously tests live defences against current threats, shows what controls block, detect, log and miss, and provides ready-to-apply fixes.",{"vendor_slug":67,"vendor_name":68,"vendor_logo":69,"product_slug":70,"product_name":71,"url":72,"description":73},"pentera","Pentera","\u002Fvendor-logos\u002Fpentera.png","pentera-platform","Pentera Platform","https:\u002F\u002Fpentera.io\u002Fpentera-platform\u002F","Runs automated, safe attacks in production to validate exploitable attack paths, prioritise proven risk and confirm fixes. Modules cover internal networks, the external attack surface and cloud.",{"vendor_slug":75,"vendor_name":76,"vendor_logo":77,"product_slug":78,"product_name":79,"url":80,"description":81},"safebreach","SafeBreach","\u002Fvendor-logos\u002Fsafebreach.png","safebreach-propagate","SafeBreach Propagate","https:\u002F\u002Fwww.safebreach.com\u002Fpropagate-attack-path-validation\u002F","Automated penetration testing that emulates lateral movement, privilege escalation and credential harvesting to show how far a breach could spread.",{"slug":83,"name":84,"problem":85,"products":86},"endpoint-detection-response","Endpoint detection and response (EDR and XDR)","Malware and hands-on-keyboard attackers on laptops and servers get spotted and stopped.",[87,95,103],{"vendor_slug":88,"vendor_name":89,"vendor_logo":90,"product_slug":91,"product_name":92,"url":93,"description":94},"sophos","Sophos","\u002Fvendor-logos\u002Fsophos.png","sophos-endpoint","Sophos Endpoint","https:\u002F\u002Fwww.sophos.com\u002Fen-us\u002Fproducts\u002Fendpoint-security","Endpoint protection with Intercept X anti-ransomware technology and EDR.",{"vendor_slug":96,"vendor_name":97,"vendor_logo":98,"product_slug":99,"product_name":100,"url":101,"description":102},"withsecure","WithSecure","\u002Fvendor-logos\u002Fwithsecure.png","elements-xdr","WithSecure Elements XDR","https:\u002F\u002Fwww.withsecure.com\u002Fen\u002Ffor-business\u002Fplatform\u002Fxdr\u002F","Endpoint detection and response with extended detection, on the Elements cloud platform.",{"vendor_slug":104,"vendor_name":105,"vendor_logo":106,"product_slug":107,"product_name":108,"url":109,"description":110},"eset","ESET","\u002Fvendor-logos\u002Feset.png","eset-protect","ESET PROTECT","https:\u002F\u002Fwww.eset.com\u002Fint\u002Fbusiness\u002Fsolutions\u002Fendpoint-protection\u002F","Endpoint protection platform with detection and response add-ons.",{"slug":112,"name":113,"problem":114,"products":115},"security-awareness-training","Security awareness training and phishing simulation","People recognise and report attacks instead of falling for them.",[116,124,130],{"vendor_slug":117,"vendor_name":118,"vendor_logo":119,"product_slug":120,"product_name":121,"url":122,"description":123},"huntress","Huntress","\u002Fvendor-logos\u002Fhuntress.png","managed-sat","Huntress Managed Security Awareness Training","https:\u002F\u002Fwww.huntress.com\u002Fplatform\u002Fsecurity-awareness-training","Security awareness training and phishing simulation, managed for you.",{"vendor_slug":125,"vendor_name":126,"vendor_logo":127,"product_slug":125,"product_name":126,"url":128,"description":129},"hoxhunt","Hoxhunt","\u002Fvendor-logos\u002Fhoxhunt.png","https:\u002F\u002Fhoxhunt.com\u002F","Adaptive phishing simulations and micro-training, with a focus on reporting.",{"vendor_slug":131,"vendor_name":132,"vendor_logo":133,"product_slug":112,"product_name":134,"url":135,"description":136},"knowbe4","KnowBe4","\u002Fvendor-logos\u002Fknowbe4.png","KnowBe4 Security Awareness Training","https:\u002F\u002Fwww.knowbe4.com\u002Fproducts\u002Fsecurity-awareness-training","Training library and simulated phishing with reporting.",[138],{"slug":139,"name":24,"logo_path":140,"roles":141},"github","\u002Fvendor-logos\u002Fgithub.png",[142],"reported_by",{"slug":144,"title":145,"body":146,"framework_refs":147,"framework_notes":155},"github-actions-pwn-request-attacks-still-viable-despite-2026-hardening","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.",[148,149,150,151,152,153,154],"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)":156,"MITRE ATT&CK T1566: Phishing":157,"NIST SP 800-53 SI-2: Flaw Remediation":158,"OWASP A06:2021 Vulnerable and Outdated Components":159,"CIS Control 7: Continuous Vulnerability Management":160,"ISO\u002FIEC 27001:2022 A.8.8: Management of technical vulnerabilities":161,"NIST CSF 2.0 PR.AA: Identity Management, Authentication, and Access Control":162},"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."]