{"answers":{"affected":"1 open source package ship an affected version, including seaweedfs.","exploited":"There is no known exploitation of CVE-2026-77368 in the wild and no public exploit code.","fix":"Upgrade seaweedfs to 4.40.0 or later.","what":"CVE-2026-77368 is a high-severity missing authorization vulnerability in seaweedfs, published on 26 Aug 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-77368 and fix it if it is affected.\n\nWhat it is: CVE-2026-77368 is a high-severity missing authorization vulnerability in seaweedfs, published on 26 Aug 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-77368 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- seaweedfs (Bitnami): affected from 4.39.0; fixed in 4.40.0\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-77368/ (Markdown: https://insights.sbomify.com/CVE-2026-77368/index.md)","id":"CVE-2026-77368","markdown":"https://insights.sbomify.com/CVE-2026-77368/index.md","name":"CVE-2026-77368","record":{"aliases":["BIT-seaweedfs-2026-77368","GHSA-99q7-x53r-6j4g","MINI-2xqh-mc9j-qm78"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify","data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Distributed storage system","requires_auth":"low_privilege","summary":"Authenticated tenants can hijack upload sessions to write or read files in paths forbidden by their JWT prefix restrictions.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"SeaweedFS is a distributed storage system for files and blobs. In version 4.39, the filer's TUS resumable-upload handler checks JWT allowed_prefixes scoping only when a session is created, letting a low-privilege tenant hijack another tenant's upload session to write content to filer paths their own token forbids. The HEAD, PATCH, and DELETE verbs that act on an existing session by its id never verify that the session's stored target path falls within the caller's allowed prefixes, so a tenant who obtains another upload's session identifier can PATCH attacker bytes into it and, on completion, have the file land at the victim's out-of-scope path. The same token can also DELETE other tenants' sessions and HEAD them to read upload progress and size, defeating the JWT prefix isolation. This vulnerability only affects deployments that configure filer JWT signing and have TUS uploads enabled. This issue is fixed in version 4.40.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"SeaweedFS: Authenticated Cross-Prefix IDOR in Filer TUS Handler Enables Arbitrary Write to Tenant-Forbidden Paths","id":"CVE-2026-77368","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":1,"n_references":3,"next":{"headline":"Redash: DuckDB query runner allows arbitrary file read/write via unrestricted external access","id":"CVE-2026-77371"},"packages":[{"ecosystem":"Bitnami","fixed":["4.40.0"],"introduced":["4.39.0"],"last_affected":[],"package":"seaweedfs","purl":"pkg:bitnami/seaweedfs","source":"BIT-seaweedfs-2026-77368"}],"prev":{"headline":"obsidian-tc tokens can access arbitrary configured vaults","id":"CVE-2026-77366"},"products":["seaweedfs"],"published":"2026-08-26","related":[],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"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-08-27","vendors":["seaweedfs"]},"summary":"Authenticated tenants can hijack upload sessions to write or read files in paths forbidden by their JWT prefix restrictions.","url":"https://insights.sbomify.com/CVE-2026-77368/"}