Is this vulnerability remotely exploitable?

Yes. Any GitHub user who can fork the jellyfin/jellyfin-ios repository and open a pull request can potentially trigger the vulnerable workflow, assuming the misconfiguration remains in place.

What level of access does an attacker need?

Only standard contributor capabilities are required: the attacker needs to create a fork and submit a pull request. No prior write access to the repository or organization is needed because the vulnerability arises from the workflow's elevated permissions.

What is the safest general fix pattern for this issue?

The safest fix pattern is to redesign the workflow to follow least-privilege principles: run untrusted PR code with read-only permissions and no sensitive secrets, isolate privileged operations to trusted branches or manually approved workflows, and minimize token scopes across all jobs.

Severity:

CRITICAL RISK

(10.0)

Excessive GitHub Actions Permissions (CWE-269) in Jellyfin iOS CI Workflow

CVE-2026-31852

Published:

Mar 11, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-918

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

Unauthorized Access to Internal Resources via SSRF

May 6, 2026

CWE-863

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Privilege Escalation via Bypassed Access Control

May 6, 2026

Vulnerability Type

Category:

Improper Authorization / Permission Misconfiguration in CI/CD

CWE:

CWE-269

Impact:

Repository Takeover and CI/CD Supply Chain Compromise

Severity:

CRITICAL RISK

(10.0)

CVSS Version:

3.1

Vulnerability Type

Category:

Improper Authorization / Permission Misconfiguration in CI/CD

CWE:

CWE-269

Impact:

Repository Takeover and CI/CD Supply Chain Compromise

Severity:

CRITICAL RISK

(10.0)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Excessive GitHub Actions Permissions (CWE-269) in Jellyfin iOS CI Workflow

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal