Wednesday, November 18, 2026

De-fanging dangerous triggers in GitHub Actions across an organization

Authors: Mike Fiedler, Seth Larson

On December 2, 2026, GitHub will start blocking the pull_request_target trigger by default in public repositories. If that sentence means nothing to you, this post is for you. If it fills you with dread, it is also for you.

The short version: a handful of GitHub Actions triggers let a stranger on the internet start a workflow that may have access to your secrets. On a GitHub Team or Enterprise plan, you can turn them off for every repository in your organization with one policy. On a Free plan, you can do it one repository at a time. Set the policy up, check what it would block, then enforce it.

Mike Fiedler, PyPI Safety and Security Engineer, and Seth Larson, Security Developer in Residence, have removed dangerous triggers and applied these policies to the Python Software Foundation (PSF) stewarded GitHub organizations (psf, python, pypi). They also wrote up technical documentation on how to roll these policies out to your own projects and organizations. The full details and technical documentation are available on the Alpha-Omega blog.

Have dangerous triggers caused real incidents?

Yes, repeatedly. A few that have affected projects hosted on PyPI directly:

  • Ultralytics, December 2024. The project's GitHub Actions workflows were compromised and the build cache was poisoned, which put malicious releases on PyPI. Seth wrote PyPI's analysis. William Woodruff's write-up traces the entry point to a pull_request_target workflow.

  • LiteLLM and Telnyx, March 2026. Malicious releases of both packages were published after an API token was exposed through an exploited Trivy dependency. StepSecurity traced the Trivy compromise back to a pull_request_target workflow exploited three weeks earlier. We worked with both maintainer teams on token rotation, release removals, and moving to Trusted Publishers, which both projects have since adopted.

  • elementary-data, April 2026. A workflow triggered by comments puts the comment text straight into a shell script. One crafted comment on a pull request ran with a token that could be written to the repository. The attacker used it to commit a malicious file and push a release tag, and the project's own release pipeline published the result to PyPI.

The maintainers behind these projects weren't careless. These triggers look harmless in a workflow file, and the unsafe version is one line away from the safe one.

Why are these triggers dangerous?

Insecure triggers can run workflows with access to your secrets, and a stranger can start them.

When someone opens a pull request from a fork, the pull_request trigger runs their code with a read-only token and no secrets. That's the safe one.

pull_request_target looks almost the same in a workflow file and behaves very differently. It runs with a read/write token and access to your repository and organization secrets. GitHub built it for chores like labeling pull requests from forks, where the workflow never touches the contributor's code. The trouble starts when a workflow checks out the pull request and runs it anyway:

on: pull_request_target
jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v6
        with:
          # a stranger's code
          ref: ${{ github.event.pull_request.head.sha }}  
      # running with your secrets
      - run: make test                                    

Anyone with a GitHub account can open that pull request. Their code now runs with your credentials. This is called a "pwn request", and GitHub's docs describe it as the root cause of multiple supply-chain compromises.

The issue_comment trigger carries the same risk. This trigger fires when anyone comments on an issue or pull request, and the workflow runs with the repository's token and secrets. Sometimes the victim is a "comment /test to run CI" bot that checks out the pull request and runs their code. Sometimes the workflow pastes the comment text into a templated shell command, and the comment turns out to inject different instructions into the workflow shell.

How did Alpha-Omega support this work?

Alpha-Omega is a fund and catalyst for sustainable open source security improvements. Alpha-Omega supports Mike's role as PyPI Safety & Security Engineer and Seth's role as Security Developer in Residence at the PSF.

That support is what gives us the time for the work behind this post:

  • Seth wrote PyPI's analysis of the Ultralytics attack

  • Mike and Seth worked with the LiteLLM and Telnyx maintainers during their incident, and wrote up the guidance for everyone else

  • Mike set up the event policy for the pypi GitHub organization

  • Seth is working to migrate the few remaining repositories using insecure triggers in the python GitHub organization before enabling the event policy

  • Mike and Seth wrote this guide so other organizations can do the same!

About the Python Software Foundation

The PSF is a non-profit whose mission is to promote, protect, and advance the Python programming language, and to support and facilitate the growth of a diverse and international community of Python programmers. The PSF supports the Python community using corporate sponsorships, grants, and donations. Are you interested in sponsoring or donating to the PSF so it can continue supporting Python and its community? Check out our sponsorship program, donate directly here, or contact our team! 


Friday, November 13, 2026

Python is for everyone: Join in the PSF year-end fundraiser & membership drive!

The Python Software Foundation (PSF) is the charitable organization behind Python, dedicated to advancing, supporting, and protecting the Python programming language and the community that sustains it. That mission is more than words to us; it’s the community we show up for every day. Our tiny but mighty team works hard to deliver the projects, services, and programs that allow Python to be the thriving, independent, community-driven language it is today. Some of what the PSF does includes producing PyCon US, hosting the Python Package Index (PyPI), supporting Developers in Residence, maintaining critical community infrastructure, and more.

Python is for gathering, teaching, learning, playing, researching, exploring, creating, building, working, sustaining. The list goes on and on and on! Support this year’s fundraiser with your donations and memberships to help the PSF, the Python community, and the language stay strong and sustainable. Because Python is for everyone, thanks to you. 

 

There are two direct ways to join through donate.python.org: 

  • Donate directly to the PSF! Your donation is a direct way to support and power the future of the Python programming language and community you love. Every donation makes a difference, and we work hard to make a little go a long way.
  • Become a PSF Supporting Member! When you sign up as a Supporting Member of the PSF, you become a part of the PSF, are eligible to vote in PSF elections, and help us sustain our mission with your annual support. You can sign up as a Supporting Member at the usual annual rate ($99 USD), or you can take advantage of our sliding scale option (starting at $25 USD)! 

>>> Donate or Become a Member Today! <<<

 
  

If you already donated and/or you’re already a member, you can:

  • Share the fundraiser with your regional and project-based communities: Share this blog post in your Python-related Discords, Slacks, social media accounts- wherever your Python community is! Keep an eye on our social media accounts to see the latest stories and news for the campaign.
  • Share your Python story with a call to action: We invite you to share your personal Python, PyCon, or PSF story. What impact has it made in your life, in your community, in your career? Share your story in a blog post or on your social media platform of choice and add a link to donate.python.org.
  • Ask your employer to sponsor: If your company is using Python to build its products and services, check to see if they already sponsor the PSF on our Sponsors page. If not, reach out to your organization's internal decision-makers and impress on them just how important it is for us to power the future of Python together, and send them our sponsor prospectus.

 

Your donations and support:

  • Keep Python thriving 
  • Support CPython and PyPI progress 
  • Increase security across the Python ecosystem 
  • Bring the global Python community together 
  • Make our community more diverse and robust every year

 

PSF highlights from 2026:

  • Producing another wonderful PyCon US: We welcomed 1,901 attendees to PyCon US 2026, 1,064 of whom were newcomers, at the Long Beach Convention & Entertainment Center in beautiful downtown Long Beach, CA, our first year in the city! PyCon US 2026 was packed with 7 days of content, education, and networking for the Python community, including 6 Keynote Sessions, 90 Talks (including the Charlas Spanish track and the new Future of AI with Python and Trailblazing Python Security tracks), 20 Tutorials, 25 Posters, 25+ Sprint Projects, 123 Open Spaces, 62 Booths, and 83 Sponsors!
  • Powering the inaugural Python Packaging Council election: We were excited to run the election that formed the first Python Packaging Council (PPC)—a long awaited technical decision-making body! The PPC will work to develop interoperability specifications that govern how Python packages are built, distributed, and installed. It will also coordinate efforts among packaging tool maintainers, the Python core team, and the broader community. The PSF is proud to have provided the administrative, logistical, and communications support that got the new council up and running.
  • Safeguarding PyPI against emerging threats: PyPI completed its second external security audit, carried out by Trail of Bits and funded by the Sovereign Tech Agency. The review turned up fourteen findings, two of them high severity, and PSF PyPI Safety and Security Engineer Mike Fiedler has already fixed all but two low-risk items that need larger changes. The auditors also wrote custom CodeQL queries, now part of PyPI’s automated checks, so the next bug of the same kind gets caught before it ships. Additionally, PyPI now rejects new files on releases older than 14 days, which stops anyone from grafting a malicious wheel onto a version people already trust. Meanwhile, community reporters sent in just under 1,000 malware and abuse reports in Q1, with over 40% landing in automated quarantine, protecting the Python ecosystem faster than ever. 
  • Developing and adopting the PSF’s 5 Year Strategic Plan: We’re proud to share that the PSF Board adopted the PSF Strategic Plan 2026, covering 2026 to 2031, at its July 2026 meeting! This plan took shape in the open: we shared the high-level goals in May, then published the full draft in June and invited the community to weigh in. Our new PSF Strategy page is its permanent home, where we’ll publish annual review findings and updates so the community can follow our progress. 
  • Sustaining the Python Security Response Team: As the number of vulnerability reports and CVE advisories grew 3-4X, the mostly-volunteer Python Security Response Team (PSRT) grew and adapted with it. Following the approval of PEP 811, 13 new members joined the PSRT, its first additions since 2023, and PSF Security Developer-in-Residence Seth Larson published a new security policy and threat model that helps coordinators quickly tell security-relevant reports from regular bugs. The team published 15 vulnerability advisories in Q1 and triaged and fixed a python.org API authentication vulnerability in under 48 hours, followed by a third-party audit by Trail of Bits. 
  • Empowering the Python community through Fiscal Sponsorship: We are proud to continue supporting our 20 fiscal sponsoree organizations with their initiatives and events all year round. The PSF provides 501(c)(3) tax-exempt status to fiscal sponsorees such as PyLadies and Pallets, and provides back office support so they can focus on their missions. Consider donating to your favorite PSF Fiscal Sponsoree and check out our Fiscal Sponsorees page to learn more about what each of these awesome organizations is all about!
  • Introducing the new PSF Community Partner Program: The PSF announced the introduction of the PSF Community Partner Program in 2026. This new program is designed as an “in-kind” way for us to support Python events and initiatives with non-financial assistance through the use of the PSF logo and name, as well as promotional support via sharing qualified posts on PSF official social media accounts. The PSF has welcomed almost 40 community events and initiatives to the program so far! 
  • Serving our community with grants: We brought back the PSF Grants Program in a restructured and more sustainable format after a pause in 2025. The PSF awarded approximately $60K over 44 grants awards across the world in 2026; supporting local conferences and workshops that keep Python growing and accessible to all. We also opened up applications for the PSF's Meetup Pro Network. We hope to continue grant funding rounds in the future and your participation in this year’s fundraiser fuels that effort!
  • Honoring community leaders: We honored 10 PSF Community Service Award (CSA) recipients this year across two batches. Abhijeet Mote, Elena Williams, Inessa Pawson, Kafui Alordo, Kalyan Prasad, Hugo van Kemenade, Kevin Horn, Maria Jose Molina Contreras, Paul Everitt, and Sarah Abderemane received CSAs in 2026 for their dedication, creativity, and generosity that help the PSF fulfill its mission to support and facilitate the growth of a diverse and international community of Python programmers.