{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-81028 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-81028 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-81028 is a medium-severity path traversal vulnerability in ZLMediaKit, published on 26 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-81028 and fix it if it is affected.\n\nWhat it is: CVE-2026-81028 is a medium-severity path traversal vulnerability in ZLMediaKit, published on 26 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-81028 in the wild and no public exploit code.\n\nAffected product: ZLMediaKit. 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-81028/ (Markdown: https://insights.sbomify.com/CVE-2026-81028/index.md)","id":"CVE-2026-81028","markdown":"https://insights.sbomify.com/CVE-2026-81028/index.md","name":"CVE-2026-81028","record":{"aliases":["GHSA-4j5x-jgmh-j582"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"ZLMediaKit media server","requires_auth":"high_privilege","summary":"Attackers with API access can read files outside the configured root directory due to a prefix collision flaw in the downloadFile API.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"ZLMediaKit confines the downloadFile API to a configured set of root directories with a prefix comparison that does not account for directory boundaries. The configuration loader in server/WebApi.cpp builds each root with File::absolutePath(\"\", item, true); because the relative-path argument is empty that helper returns the value without a trailing separator. The handler then accepts a requested path when start_with(file_path, root) holds, so a sibling directory whose name merely begins with the configured root string satisfies the test and is served. The only other guard rejects a path containing two dots, which this requires none of. The equivalent confinement check for the ordinary static file server in src/Http/HttpFileManager.cpp computes its root with a non-empty second argument, which appends the separator before comparing, and so is not affected. The endpoint requires the configured API secret, so this grants no privilege beyond what that secret already implies, but it reads files outside the directory the operator confined it to, and the reference container runs the server as root.","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":"ZLMediaKit downloadFile Root-Directory Confinement Bypass via Prefix Collision","id":"CVE-2026-81028","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"OpenMetadata before 2.0.0 JWT Disclosure via Unvalidated SAML and OIDC Redirect URI","id":"CVE-2026-81029"},"packages":[],"prev":{"headline":"one-api through 0.6.10 Missing Authorization on URL-Parameter Channel Pinning","id":"CVE-2026-81027"},"products":["ZLMediaKit"],"published":"2026-08-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-10-27","vendors":["ZLMediaKit"]},"summary":"Attackers with API access can read files outside the configured root directory due to a prefix collision flaw in the downloadFile API.","url":"https://insights.sbomify.com/CVE-2026-81028/"}