CVE-2026-31852
Jellyfin iOS workflow enables code execution via fork PRs, risking repo takeover.
Is CVE-2026-31852 being exploited?
Not confirmed. CVE-2026-31852 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.45% probability of exploitation in the next 30 days.
How severe is CVE-2026-31852?
CVE-2026-31852 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-31852?
Yes. A fix has been recorded for CVE-2026-31852. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-31852 affect?
CVE-2026-31852 affects Jellyfin/jellyfin-ios GitHub Actions workflow, Jellyfin iOS CI workflow. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-31852?
Limit workflow permissions; rotate secrets; monitor fork PRs
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker can execute code via fork PRs with near-full write access, enabling secret exfiltration, supply-chain risk, and org compromise.
Monitor only
- affected< 109217e75f38394b2f6e46e25dfe5a721203d3c8
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.