Repository takeover via untrusted pull-request workflow execution
Published Mar 11, 2026 · Updated Mar 11, 2026
Arbitrary code execution in Jellyfin's code-quality.yml workflow allows remote attackers to run forked pull-request code with repository privileges. The workflow uses pull_request_target, checks out the fork's head commit, and runs Jest while write permissions and repository secrets remain available. A crafted fork pull request therefore grants access to privileged tokens, enabling secret theft, repository takeover, and downstream release compromise.
Summary
What happened
Arbitrary code execution in Jellyfin's code-quality.yml workflow allows remote attackers to run forked pull-request code with repository privileges. The workflow uses pull_request_target, checks out the fork's head commit, and runs Jest while write permissions and repository secrets remain available. A crafted fork pull request therefore grants access to privileged tokens, enabling secret theft, repository takeover, and downstream release compromise.
The record
- CVE
- CVE-2026-31852
- Published
- Mar 11, 2026
- Updated
- Mar 11, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-269, T1195.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 11, 2026CVE publishedPublication date reported by the CVE source.
- Mar 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo