{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54917 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2026-54917 is a high-severity path traversal vulnerability in seaweedfs, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-54917 and fix it if it is affected.\n\nWhat it is: CVE-2026-54917 is a high-severity path traversal vulnerability in seaweedfs, published on 25 Jun 2026. 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-2026-54917 exists.\n\nAffected product: seaweedfs. 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-54917/ (Markdown: https://insights.sbomify.com/CVE-2026-54917/index.md)","id":"CVE-2026-54917","markdown":"https://insights.sbomify.com/CVE-2026-54917/index.md","name":"CVE-2026-54917","record":{"aliases":["MINI-ffj2-828w-ffrj","MINI-q3mg-m32h-9cmh"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"SeaweedFS storage system","requires_auth":"none","summary":"Attackers can access or modify data in unauthorized buckets via path traversal in SeaweedFS S3 and Iceberg gateways.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"seaweedfs","vendor":"seaweedfs"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"SeaweedFS is a distributed storage system for object storage (S3), file systems, and Iceberg tables. Prior to 4.30, the S3 API gateway and the Iceberg REST catalog gateway construct their routers with mux.NewRouter().SkipClean(true). With path cleaning disabled, a .. segment inside the URL survives routing, so a request such as `GET /bucket-A/../evil-bucket/key`, is matched as bucket=bucket-A, object=../evil-bucket/key. The captured object key is then joined into a filer path with util.JoinPath (S3) / path.Join (Iceberg), which collapse the .. server-side, so the actual read or write lands in evil-bucket. This vulnerability is fixed in 4.30.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-08-05","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":1,"refs":[{"date":"2026-08-05T01:44:54Z","kind":"github_poc","ref":"https://github.com/BiiTts/CVE-2026-54917-SeaweedFS-Cross-Bucket-Traversal","stars":0,"title":"PoC + analysis for CVE-2026-54917 — SeaweedFS S3 gateway cross-bucket path traversal (CVSS 10.0, \u003c4.30). Read/write any bucket via .. in the object key."},{"date":null,"kind":"nuclei","ref":"http/cves/2026/CVE-2026-54917.yaml","stars":null,"title":"SeaweedFS \u003c= 4.29 - Path Traversal File Write"}],"tier":"weaponised"},"has_fix":true,"headline":"SeaweedFS: Path traversal in the S3 and Iceberg REST gateways allows cross-bucket access","id":"CVE-2026-54917","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Server-side request forgery in devicetype-library","id":"CVE-2026-54918"},"packages":[],"prev":{"headline":"Code injection in devicetype-library","id":"CVE-2026-54916"},"products":["seaweedfs"],"published":"2026-06-25","related":[{"cvss_score":7,"headline":"SeaweedFS: Hard-coded SSH host key can be presented by certain standalone SFTP Helm deployments","id":"CVE-2026-100413","kev_date_added":null,"published":"2026-10-14"},{"cvss_score":6.5,"headline":"SeaweedFS Vulnerable to SQL Injection","id":"CVE-2024-40120","kev_date_added":null,"published":"2025-05-16"}],"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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-25","vendors":["seaweedfs"]},"summary":"Attackers can access or modify data in unauthorized buckets via path traversal in SeaweedFS S3 and Iceberg gateways.","url":"https://insights.sbomify.com/CVE-2026-54917/"}