● Critical · CVSS 10

How to Fix CVE-2026-31852: CWE-269: Improper Privilege Management in code-quality.yml

Q: Is CVE-2026-31852 being actively exploited?

Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.

Q: How severe is CVE-2026-31852?

CVSS rates it 10 (Critical). Use that score to set your patch priority next to the other items in your queue.

Q: Do I have to take code-quality.yml offline to apply the patch?

It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.

Q: What if my vulnerability scanner still flags CVE-2026-31852 after I patch?

Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-2986: Cross-site scripting in Contextual Related Posts — Cross-site scripting in Contextual Related Posts
How to Fix CVE-2026-3570: Critical Vulnerability in Smarter Analytics — Critical Vulnerability in Smarter Analytics
How to Fix CVE-2026-1706: Cross-site scripting in All-in-One Video Gallery , Cross-site scripting in All-in-One Video Gallery
How to Fix CVE-2026-2922: CWE-787: Out-of-bounds Write in GStreamer , CWE-787: Out-of-bounds Write in GStreamer
How to Fix CVE-2026-31953: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') , CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

*By Sai Kiran Pandrala*

⚡ At a glance


Severity	CVSS 10, Critical
Actively exploited?	No
Affected	Jellyfin code-quality.yml (< 109217e75f38394b2f6e46e25dfe5a721203d3c8)
Fixed in	109217e75f38394b2f6e46e25dfe5a721203d3c8
Type (CWE)	CWE-269: Improper Privilege Management

What is CVE-2026-31852?

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.

In practical terms, a successful attacker gets remote code execution on the affected system. There is no confirmed in-the-wild exploitation listed in CISA's KEV catalog at the time of writing, but the CVSS rating still warrants prompt patching.

Am I affected?

You're affected if you run Jellyfin code-quality.yml at any version in the Affected row above. Use these probes to find your installed build:


# Confirm the installed version via your package manager
dpkg -l | grep -i code-quality.yml   # Debian/Ubuntu
rpm -qa | grep -i code-quality.yml   # RHEL/CentOS/Rocky

How to fix CVE-2026-31852

The primary fix is to upgrade to the patched build listed in the Fixed in row above (109217e75f38394b2f6e46e25dfe5a721203d3c8). Pick the platform that matches your install and run the commands below.

Linux (Ubuntu / Debian)


sudo apt-get update
sudo apt-get install --only-upgrade code-quality-yml
# Confirm the installed version meets or exceeds 109217e75f38394b2f6e46e25dfe5a721203d3c8
dpkg -s code-quality-yml | grep ^Version

Linux (RHEL / CentOS / Rocky)


sudo dnf upgrade --security code-quality-yml -y
rpm -q code-quality-yml

Windows (PowerShell, admin)


# Try winget first
winget upgrade --id 'Jellyfin.code-quality.yml' --silent --accept-source-agreements --accept-package-agreements
# If winget does not know the product, download the patched installer from the vendor and:
Start-Process -FilePath "$env:TEMP\codequalityyml-109217e75f38394b2f6e46e25dfe5a721203d3c8.msi" -ArgumentList '/qn /norestart' -Wait

PowerShell script (Windows) - detect, back up, upgrade, verify, log


# Run as Administrator
$ErrorActionPreference = 'Stop'
$log = "$env:ProgramData\codequalityyml-Patch-CVE-2026-31852.log"
function Write-Log($msg) { "$(Get-Date -Format s)  $msg" | Tee-Object -FilePath $log -Append }

Write-Log "Starting CVE-2026-31852 remediation for Jellyfin code-quality.yml"

# 1. Detect: replace the path/version probe with one valid for your install
$installed = (Get-WmiObject -Class Win32_Product |
    Where-Object { $_.Name -like '*code-quality.yml*' } |
    Select-Object -First 1 -ExpandProperty Version)
Write-Log "Detected version: $installed"

if (-not $installed) {
    Write-Log "Product not installed on this host; nothing to do."
    return
}
if ([version]$installed -ge [version]'109217e75f38394b2f6e46e25dfe5a721203d3c8') {
    Write-Log "Already at fixed version $installed; no action needed."
    return
}

# 2. Backup configuration to a timestamped folder
$backup = "$env:ProgramData\codequalityyml-Backup-$(Get-Date -Format yyyyMMdd-HHmm)"
New-Item -ItemType Directory -Path $backup -Force | Out-Null
# Adjust the source path to match your install
$src = "$env:ProgramFiles\Jellyfin\code-quality.yml"
if (Test-Path $src) { Copy-Item -Path $src -Destination $backup -Recurse -Force }
Write-Log "Backed up config to $backup"

# 3. Apply the patched installer (place the verified file on a share or staging path)
$installer = "$env:TEMP\codequalityyml-109217e75f38394b2f6e46e25dfe5a721203d3c8.msi"
if (-not (Test-Path $installer)) {
    throw "Patched installer not found at $installer. Stage it from your software repo first."
}
Start-Process msiexec.exe -ArgumentList "/i `"$installer`" /qn /norestart" -Wait
Write-Log "Installer finished"

# 4. Verify
$verify = (Get-WmiObject -Class Win32_Product |
    Where-Object { $_.Name -like '*code-quality.yml*' } |
    Select-Object -First 1 -ExpandProperty Version)
if ([version]$verify -ge [version]'109217e75f38394b2f6e46e25dfe5a721203d3c8') {
    Write-Log "SUCCESS: now at $verify (>= 109217e75f38394b2f6e46e25dfe5a721203d3c8)"
} else {
    Write-Log "FAILURE: still at $verify after install"
    exit 1
}

Bash script (Linux) - detect, back up, upgrade, verify, log


#!/usr/bin/env bash
set -euo pipefail
LOG=/var/log/code-quality-yml-patch-cve-2026-31852.log
log()  { echo "$(date -Iseconds)  $*" | tee -a "$LOG"; }

log "Starting CVE-2026-31852 remediation for Jellyfin code-quality.yml"

# 1. Detect installed version (works for deb and rpm packages)
if command -v dpkg >/dev/null && dpkg -s code-quality-yml >/dev/null 2>&1; then
    CURRENT=$(dpkg-query -W -f='${Version}' code-quality-yml)
    PKG_MGR=apt
elif command -v rpm >/dev/null && rpm -q code-quality-yml >/dev/null 2>&1; then
    CURRENT=$(rpm -q --queryformat '%{VERSION}' code-quality-yml)
    PKG_MGR=dnf
else
    log "code-quality-yml not installed via apt or rpm; check your package manager or vendor instructions."
    exit 0
fi
log "Detected: code-quality-yml=$CURRENT (manager=$PKG_MGR)"

# 2. Backup config
BACKUP=/var/backups/code-quality-yml-$(date +%Y%m%d-%H%M)
mkdir -p "$BACKUP"
for d in /etc/code-quality-yml /etc/${pkg%%-*} ; do
    [ -d "$d" ] && cp -a "$d" "$BACKUP/" && log "Backed up $d to $BACKUP"
done

# 3. Upgrade
if [ "$PKG_MGR" = apt ]; then
    sudo apt-get update -y
    sudo apt-get install --only-upgrade -y code-quality-yml
else
    sudo dnf upgrade --security -y code-quality-yml
fi

# 4. Verify
if [ "$PKG_MGR" = apt ]; then
    NEW=$(dpkg-query -W -f='${Version}' code-quality-yml)
else
    NEW=$(rpm -q --queryformat '%{VERSION}' code-quality-yml)
fi
log "After upgrade: $NEW"

# Optionally compare against 109217e75f38394b2f6e46e25dfe5a721203d3c8 with dpkg --compare-versions or sort -V
log "Done. Restart the affected service if the package install did not."

If you can't patch immediately

These are runnable hardening commands. They reduce blast radius but they're not a replacement for the vendor patch.

Rate-limit and log the affected endpoint at the reverse proxy


limit_req_zone $binary_remote_addr zone=admin:10m rate=10r/m;
location /<vulnerable-path> {
    limit_req zone=admin burst=5 nodelay;
    access_log /var/log/nginx/admin-access.log combined;
    proxy_pass http://backend;
}

How to verify the fix worked

Run the version probe again and confirm the running build matches the Fixed in row above.


# Confirm the running build matches the patched version listed by the vendor
# Example for Linux package installs:
dpkg -l | grep -i "code-quality.yml"   # Debian/Ubuntu
rpm -qa | grep -i "code-quality.yml"   # RHEL/CentOS/Rocky

Expected output: the package version should meet or exceed 109217e75f38394b2f6e46e25dfe5a721203d3c8.

Then re-run any vulnerability scanner you used previously and confirm the finding for CVE-2026-31852 has cleared. Sweep your logs for the indicators of compromise listed in the vendor or CISA advisory, especially if the system was internet-reachable during the disclosure window.

Frequently asked questions

Is CVE-2026-31852 being actively exploited?