CVE-2026-35033
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 · uneditedJellyfin is an open source self hosted media server. Versions prior to 10.11.7 contain an unauthenticated arbitrary file read vulnerability via ffmpeg argument injection through the StreamOptions query parameter parsing mechanism. The ParseStreamOptions method in StreamingHelpers.cs adds any lowercase query parameter to a dictionary without validation, bypassing the RegularExpression attribute on the level controller parameter, and the unsanitized value is concatenated directly into the ffmpeg command line. By injecting a drawtext filter with a textfile argument, an attacker can read arbitrary server files such as /etc/shadow and exfiltrate their contents as text rendered in the video stream response. The vulnerable /Videos/{itemId}/stream endpoint has no Authorize attribute, making this exploitable without authentication, though item GUIDs are pseudorandom and require an authenticated user to obtain. This issue has been fixed in version 10.11.7.
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 confidenceJellyfin versions prior to 10.11.7 contain an unauthenticated arbitrary file read vulnerability. The ParseStreamOptions method in StreamingHelpers.cs adds lowercase query parameters to a dictionary without validation, bypassing the RegularExpression attribute. These unsanitized values are concatenated directly into the ffmpeg command line, allowing attackers to inject a drawtext filter with a textfile argument to read arbitrary server files like /etc/shadow and exfiltrate contents as rendered text in the video stream.
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< 10.11.7CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Jellyfin versionAccess the Jellyfin web dashboard, navigate to Dashboard > General > Server, and note the displayed version number. Alternatively, query the API endpoint /System/Info or check the installed package via system package manager (dpkg, rpm, etc.).Affected if The version is lower than 10.11.7 (e.g., 10.11.6, 10.10.x, 10.9.x, etc.).
-
Verify StreamingHelpers.cs file versionLocate the StreamingHelpers.cs file in the Jellyfin installation directory under Server/MediaEncoding/ or similar path. Check the file header or git history for version information related to the ParseStreamOptions method.Affected if The file corresponds to a version prior to 10.11.7 or contains the vulnerable ParseStreamOptions method without proper input sanitization.
-
Confirm streaming endpoint accessibilityTest access to Jellyfin streaming endpoints (e.g., /Videos/{id}/stream or /Items/{id}/PlaybackInfo) without authentication. Use a tool like curl to send a request with lowercase query parameters such as ?textfile=/etc/passwd.Affected if The endpoint accepts unauthenticated requests and processes the query parameters without validation.
-
Inspect ffmpeg command constructionEnable debug logging in Jellyfin (Dashboard > Logging > Log Level set to Debug or Trace), then trigger a stream request with a test parameter. Examine the generated ffmpeg command in the logs to verify if raw query values appear in the command line.Affected if The ffmpeg command line contains unsanitized user-controlled input from query parameters, indicating the vulnerability is present.
A system is affected if it runs any Jellyfin version lower than 10.11.7 and exposes streaming functionality to unauthenticated users, allowing arbitrary file access via the drawtext filter injection.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.11.7
Upgrade to Jellyfin version 10.11.7 or later to patch this vulnerability. Until then, consider restricting access to the media server and monitoring for suspicious stream requests with unusual query parameters.
10.11.7
- 1. Back up the current Jellyfin installation and all data directories before proceeding
- 2. Upgrade Jellyfin to version 10.11.7 or later following the official upgrade guide for your installation method (docker, apt, yum, or manual)
- 3. Restart the Jellyfin service to ensure the new version is loaded
- 4. Verify the version number matches 10.11.7 or higher in the Jellyfin dashboard under Dashboard > General
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35033 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-35033 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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