CVE-2026-31852: Jellyfin Possible Organization/Secret Compromise from dangerous CI implementation
Jellyfin is an open-source media system. The code-quality.yml GitHub Actions workflow in jellyfin/jellyfin-ios is vulnerable to arbitrary code execution via pull requests from forked repositories. Due to the workflow's elevated permissions (nearly all write permissions), this vulnerability enables full repository takeover of jellyfin/jellyfin-ios, exfiltration of highly privileged secrets, Apple App Store supply chain attack, GitHub Container Registry (ghcr.io) package poisoning, and full jellyfin organization compromise via cross-repository token usage. Note: This is not a code vulnerability, but a vulnerability in the GitHub Actions workflows. No new version is required for this GHSA and end users do not need to take any actions.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-31852?
CVE-2026-31852 has a high severity rating due to the potential for arbitrary code execution from forked repositories.
How do I fix CVE-2026-31852?
To fix CVE-2026-31852, the GitHub Actions workflow should be modified to securely handle pull requests and avoid executing code from untrusted sources.
Which versions of Jellyfin are affected by CVE-2026-31852?
CVE-2026-31852 affects the Jellyfin iOS application as indicated in the vulnerability report.
What could be the impact of CVE-2026-31852?
The impact of CVE-2026-31852 may include unauthorized access or control over the application environment through arbitrary code execution.
Is CVE-2026-31852 a widespread vulnerability?
CVE-2026-31852 is specific to the Jellyfin project, affecting its iOS application, but indicative of a broader issue in CI/CD pipeline security.