dbcve.org
JellyfinApplication

CVE-2026-31852

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-11
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The code-quality.yml GitHub Actions workflow in jellyfin/jellyfin-ios allows arbitrary code execution via pull requests from forked repositories because the workflow has nearly all write permissions enabled. This enables attackers to take over the repository, steal secrets, poison container images, and potentially compromise the entire Jellyfin organization.

MitigationRestrict workflow permissions to minimum required (read-only where possible), avoid triggering workflows on pull requests from forks, or require approval before running external PR workflows.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JellyfinApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the code-quality.yml workflow file
    Inspect the repository at .github/workflows/code-quality.yml or search for any workflow file with 'code-quality' in the name under .github/workflows/
    Affected if The workflow file exists in the repository
  2. Check workflow permissions configuration
    Open the workflow YAML file and look for the 'permissions:' block at the top level or within the job. Check if permissions are set to write-all, contents: write, or similar overly permissive settings
    Affected if Permissions include write access to contents, pull-requests, or other sensitive scopes without explicit justification
  3. Verify the workflow triggers on pull_request events
    In the workflow file, locate the 'on:' section and check if 'pull_request' or 'pull_request_target' is listed as a trigger
    Affected if The workflow triggers on pull_request or pull_request_target events from external forks
  4. Confirm write permissions are enabled for the workflow
    Look for 'permissions:' at the workflow level with values like 'contents: write', 'pull-requests: write', or an unset permissions block that defaults to full write access
    Affected if The workflow has write permissions enabled and can be triggered by external pull requests

If the code-quality.yml workflow exists, has write permissions configured, and triggers on pull request events from forks, the repository is vulnerable to arbitrary code execution via external PRs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Restrict workflow permissions to minimum required (read-only where possible), avoid triggering workflows on pull requests from forks, or require approval before running external PR workflows.

Recommended fix High confidence
  1. Navigate to the jellyfin/jellyfin-ios repository on GitHub
  2. Locate the .github/workflows/code-quality.yml file
  3. Apply the fix from commit 109217e75f38394b2f6e46e25dfe5a721203d3c8, which typically involves restricting workflow permissions to read-only for pull requests from forks (e.g., using permissions: contents: read)
  4. Commit the updated workflow file to the repository
  5. Verify the workflow runs correctly after the change

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jellyfin Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,670
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-31852 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-31852 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data