CVE-2026-31852 Jellyfin Possible Organization/Secret Compromise from dangerous CI implementation

Critical 10.0 Published 11 Mar 2026 Updated 11 Mar 2026

Attackers can execute arbitrary code via pull requests to compromise the repository, steal secrets, and poison supply chains due to excessive CI permissions.

Exploited in the wild: Not known
Login needed: Not needed
Attackable: Over the internet
Victim action needed: Not needed
Fix: Available

What is CVE-2026-31852?

CVE-2026-31852 is a critical vulnerability in jellyfin code-quality.yml, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

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.

Weakness: CWE-269

Which versions are affected by CVE-2026-31852?

It affects 1 product.

Products include Jellyfin Jellyfin.

How do I fix CVE-2026-31852?

Change a configuration setting.

Is CVE-2026-31852 being exploited?

There is no known exploitation of CVE-2026-31852 in the wild and no public exploit code.

Public exploit code: 1 proofs of concept on GitHub.

Sources

Also known as GHSA-7qhm-2m45-7fmh, MINI-r6x8-62g2-79xc.