{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-49096 exists.","fix":"No fix has been published for CVE-2023-49096 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-49096 is a high-severity command injection vulnerability in jellyfin, published on 6 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-49096 and fix it if it is affected.\n\nWhat it is: CVE-2023-49096 is a high-severity command injection vulnerability in jellyfin, published on 6 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-49096 exists.\n\nAffected product: jellyfin. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-49096/ (Markdown: https://insights.sbomify.com/CVE-2023-49096/index.md)","id":"CVE-2023-49096","markdown":"https://insights.sbomify.com/CVE-2023-49096/index.md","name":"CVE-2023-49096","record":{"aliases":["GHSA-866x-wj5j-2vf4"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Jellyfin media server","requires_auth":"none","summary":"Unauthenticated attackers can inject FFmpeg arguments via codec parameters, potentially executing code or modifying files.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"jellyfin","vendor":"jellyfin"}],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-88","name":"Improper Neutralization of Argument Delimiters in a Command"}],"description":"Jellyfin is a Free Software Media System for managing and streaming media. In affected versions there is an argument injection in the VideosController, specifically the `/Videos/\u003citemId\u003e/stream` and `/Videos/\u003citemId\u003e/stream.\u003ccontainer\u003e` endpoints which are present in the current Jellyfin version. Additional endpoints in the AudioController might also be vulnerable, as they differ only slightly in execution. Those endpoints are reachable by an unauthenticated user. In order to exploit this vulnerability an unauthenticated attacker has to guess an itemId, which is a completely random GUID. It’s a very unlikely case even for a large media database with lots of items. Without an additional information leak, this vulnerability shouldn’t be directly exploitable, even if the instance is reachable from the Internet. There are a lot of query parameters that get accepted by the method. At least two of those, videoCodec and audioCodec are vulnerable to the argument injection. The values can be traced through a lot of code and might be changed in the process. However, the fallback is to always use them as-is, which means we can inject our own arguments. Those arguments land in the command line of FFmpeg. Because UseShellExecute is always set to false, we can’t simply terminate the FFmpeg command and execute our own. It should only be possible to add additional arguments to FFmpeg, which is powerful enough as it stands. There is probably a way of overwriting an arbitrary file with malicious content. This vulnerability has been addressed in version 10.8.13. Users are advised to upgrade. There are no known workarounds for this vulnerability.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Argument Injection in FFmpeg codec parameters in Jellyfin","id":"CVE-2023-49096","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2023"},"n_packages":0,"n_references":6,"next":{"headline":"ZITADEL vulnerable account takeover via malicious host header injection","id":"CVE-2023-49097"},"packages":[],"prev":{"headline":"nexkey allows arbitrary users to impersonate any remote user due to missing signature validation","id":"CVE-2023-49095"},"products":["jellyfin"],"published":"2023-12-06","related":[{"cvss_score":10,"headline":"Jellyfin: Potential RCE via subtitle upload path traversal + .strm chain","id":"CVE-2026-35031","kev_date_added":null,"published":"2026-04-14"},{"cvss_score":10,"headline":"Jellyfin Possible Organization/Secret Compromise from dangerous CI implementation","id":"CVE-2026-31852","kev_date_added":null,"published":"2026-03-11"},{"cvss_score":9.3,"headline":"Jellyfin: Potential SSRF + Arbitrary file read via stream argument injection","id":"CVE-2026-35033","kev_date_added":null,"published":"2026-04-14"},{"cvss_score":9.1,"headline":"jellyfin-web has a stored cross-site scripting vulnerability in devices.js","id":"CVE-2023-30627","kev_date_added":null,"published":"2023-04-24"},{"cvss_score":8.8,"headline":"Jellyfin vulnerable to directory traversal and file write causing arbitrary code execution","id":"CVE-2023-30626","kev_date_added":null,"published":"2023-04-24"},{"cvss_score":8.8,"headline":"Incorrect Access Control and Cross Site Scripting in Jellyfin","id":"CVE-2022-35909","kev_date_added":null,"published":"2022-08-19"},{"cvss_score":8.6,"headline":"Jellyfin: Potential SSRF + Arbitrary file read via LiveTV M3U tuner","id":"CVE-2026-35032","kev_date_added":null,"published":"2026-04-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-05-28","vendors":["jellyfin"]},"summary":"Unauthenticated attackers can inject FFmpeg arguments via codec parameters, potentially executing code or modifying files.","url":"https://insights.sbomify.com/CVE-2023-49096/"}