{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-35034 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-35034 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-35034 is a medium-severity denial of service vulnerability in jellyfin, published on 14 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-35034 and fix it if it is affected.\n\nWhat it is: CVE-2026-35034 is a medium-severity denial of service vulnerability in jellyfin, published on 14 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-35034 in the wild and no public exploit code.\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-2026-35034/ (Markdown: https://insights.sbomify.com/CVE-2026-35034/index.md)","id":"CVE-2026-35034","markdown":"https://insights.sbomify.com/CVE-2026-35034/index.md","name":"CVE-2026-35034","record":{"aliases":["GHSA-v2jv-54xj-h76w"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Jellyfin media server","requires_auth":"low_privilege","summary":"An authenticated user can cause a denial of service in Jellyfin by creating SyncPlay groups with excessively large names, leading to memory exhaustion.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"jellyfin","vendor":"jellyfin"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"Jellyfin is an open source self hosted media server. Versions prior to 10.11.7 contain a denial of service vulnerability in the SyncPlay group creation endpoint (POST /SyncPlay/New), where an authenticated user can create groups with names of unlimited size due to insufficient input validation. By sending large payloads combined with arbitrary group IDs, an attacker can lock out the endpoint for other clients attempting to join SyncPlay groups and significantly increase the memory usage of the Jellyfin process, potentially leading to an out-of-memory crash. This issue has been fixed in version 10.11.7.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Jellyfin: Potential Application DoS from excessively large SyncPlay group names","id":"CVE-2026-35034","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"CI4MS: Company Information Public-Facing Page Full Platform Compromise \u0026 Full Account Takeover for All Roles \u0026 Privilege-Escalation via System Settings Company Information Stored DOM XSS","id":"CVE-2026-35035"},"packages":[],"prev":{"headline":"Jellyfin: Potential SSRF + Arbitrary file read via stream argument injection","id":"CVE-2026-35033"},"products":["jellyfin"],"published":"2026-04-14","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-15","vendors":["jellyfin"]},"summary":"An authenticated user can cause a denial of service in Jellyfin by creating SyncPlay groups with excessively large names, leading to memory exhaustion.","url":"https://insights.sbomify.com/CVE-2026-35034/"}