{"answers":{"affected":"1 open source package ship an affected version, including seaweedfs.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-58371 exists.","fix":"Upgrade seaweedfs to 4.30.0 or later.","what":"CVE-2026-58371 is a low-severity cross-site scripting vulnerability in seaweedfs, published on 30 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-58371 and fix it if it is affected.\n\nWhat it is: CVE-2026-58371 is a low-severity cross-site scripting vulnerability in seaweedfs, published on 30 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-58371 exists.\n\nAffected packages and fixed versions:\n- seaweedfs (Bitnami): affected all versions; fixed in 4.30.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-58371/ (Markdown: https://insights.sbomify.com/CVE-2026-58371/index.md)","id":"CVE-2026-58371","markdown":"https://insights.sbomify.com/CVE-2026-58371/index.md","name":"CVE-2026-58371","record":{"aliases":["BIT-seaweedfs-2026-58371","GHSA-7cpf-frp7-pm75"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"SeaweedFS distributed storage","requires_auth":"none","summary":"Attackers can read sensitive cluster topology and file metadata via JSONP injection in SeaweedFS, potentially leading to further compromise.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":2.3,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"SeaweedFS before 4.30 reflects the callback query parameter verbatim into responses served with Content-Type application/javascript in the shared writeJson helper (weed/server/common.go), with no callback-name validation, no X-Content-Type-Options: nosniff header, and no CORS allow-list. Every JSON endpoint that uses writeJson - including the unauthenticated master endpoints /dir/status, /dir/lookup and /cluster/status, the volume server /status, and the filer directory listing, all reachable in the default configuration (no -whiteList, no security.toml, bound to 0.0.0.0) - can therefore be loaded cross-origin via a script tag with a chosen callback, letting a third-party web page read cluster topology, volume server URLs and gRPC ports, file identifiers, and directory listings. Because the callback string is reflected at the start of the body and no nosniff header is sent, MIME-sniffing clients may also interpret the reflected content as HTML.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"SeaweedFS \u003c 4.30 - Cross-Origin Information Disclosure via Unvalidated JSONP callback Parameter","id":"CVE-2026-58371","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"xss","year":"2026"},"n_packages":1,"n_references":5,"next":{"headline":"SeaweedFS \u003c 4.34 - Cross-Bucket Object Deletion via DeleteObjects Request-Body Keys","id":"CVE-2026-58372"},"packages":[{"ecosystem":"Bitnami","fixed":["4.30.0"],"introduced":["0"],"last_affected":[],"package":"seaweedfs","purl":"pkg:bitnami/seaweedfs","source":"BIT-seaweedfs-2026-58371"}],"prev":{"headline":"Woodpecker \u003c 3.15.0 - GitLab Approval Gate Bypass via Spoofable Commit Author Name","id":"CVE-2026-58370"},"products":["seaweedfs"],"published":"2026-06-30","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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-14","vendors":["seaweedfs"]},"summary":"Attackers can read sensitive cluster topology and file metadata via JSONP injection in SeaweedFS, potentially leading to further compromise.","url":"https://insights.sbomify.com/CVE-2026-58371/"}