GHSL-2026-199: Code execution in DataDog/trivy API Diff Check workflow

Published Sep 4, 2026
·
Updated

The API Diff Check workflow invokes a pull request-controlled local action in a privileged pullrequesttarget job. An external contributor can execute arbitrary code with a write-scoped GITHUBTOKEN and access the ORGREPOTOKEN secret.

Other sources

The API Diff Check workflow runs on pullrequesttarget, checks out a pull request’s merge ref, and then invokes the checkout-relative ./.github/actions/setup-go composite action. An external pull request author can modify that local action and execute arbitrary code in the privileged base-repository workflow. The job grants its GITHUBTOKEN pull-requests: write and issues: write permissions. The attacker-controlled code can steal the repository-level ORGREPOTOKEN secret before the later conditional step that explicitly references it.

— GitHub Security Lab

Affected Software

1 affected component
Datadog Trivy

Event History

Sep 4, 2026
Advisory Published
via GitHub Security Lab·12:00 AM
Data Sourced
via GitHub Security Lab·12:00 AM
Description
Data Sourced
via GitHub Security Lab·12:00 AM
WeaknessAffected Software

Frequently Asked Questions

1

Who can exploit this workflow weakness?

An external contributor who can open or influence a pull request can exploit it, because the affected job uses pull_request_target while invoking a pull request-controlled local action.

2

What access could an attacker gain through successful exploitation?

The attacker can execute arbitrary code with a write-scoped GITHUB_TOKEN and access to the ORG_REPO_TOKEN secret.

3

Is a repository affected only when maintainers run the workflow manually?

No. The issue is in the API Diff Check workflow's privileged pull_request_target job, which processes pull request-controlled action content.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203