CVE-2026-49247

See a problem?
Please try reporting it to the source first.

Source

https://cve.org/CVERecord?id=CVE-2026-49247

Import Source

https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2026-49247.json

JSON Data

https://api.test.osv.dev/v1/vulns/CVE-2026-49247

Aliases

GHSA-jg92-mrxq-vv75

Published

2026-06-24T18:18:46.137Z

Modified

2026-06-27T11:55:26.779578085Z

Severity

8.8 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H CVSS Calculator

Summary

Jellyfin: Potential Authenticated path traversal in /ClientLog/Document

Details

Jellyfin is an open source self hosted media server. From 10.9.0 until 10.11.10, the POST /ClientLog/Document endpoint accepts the Authorization header's Client and Version fields and uses them unsanitized as components of the on-disk filename when persisting client-uploaded log documents. As a result, any authenticated non-admin user can include ../ sequences in the Client field to cause Jellyfin to write attacker-controlled content to arbitrary paths reachable by the Jellyfin service user, with a forced .log suffix. This vulnerability is fixed in 10.11.10.

Database specific

{
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/49xxx/CVE-2026-49247.json",
    "cwe_ids": [
        "CWE-22"
    ],
    "cna_assigner": "GitHub_M"
}

References

Affected packages

Git / github.com/jellyfin/jellyfin

Affected ranges

Type

GIT

Repo

https://github.com/jellyfin/jellyfin

Events

Introduced

327f92bb2e26cf058a14e7eff34ed2798dc8fc0d

Fixed

4b4b4cd94d8d3fe20b2b2b576edbc5cfa933fe07

Database specific

{
    "source": "AFFECTED_FIELD",
    "extracted_events": [
        {
            "introduced": "10.9.0"
        },
        {
            "fixed": "10.11.10"
        }
    ]
}

Database specific

source

"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2026-49247.json"