{"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-77611 exists.","fix":"Upgrade seaweedfs to 4.40.0 or later.","what":"CVE-2026-77611 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-77611 and fix it if it is affected.\n\nWhat it is: CVE-2026-77611 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77611 exists.\n\nAffected packages and fixed versions:\n- seaweedfs (Bitnami): affected all versions; 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-77611/ (Markdown: https://insights.sbomify.com/CVE-2026-77611/index.md)","id":"CVE-2026-77611","markdown":"https://insights.sbomify.com/CVE-2026-77611/index.md","name":"CVE-2026-77611","record":{"aliases":["BIT-seaweedfs-2026-77611","GHSA-9x53-cjpr-m682","MINI-rhv5-hf6x-q63x"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Distributed storage system","requires_auth":"low_privilege","summary":"Authenticated users can bypass object-scope restrictions to overwrite unrelated files at the bucket root via PutObjectAcl.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"SeaweedFS is a distributed storage system for files and blobs. In versions prior to 4.40, an authenticated S3 principal with permissions scoped to a nested object key can overwrite a different object outside that scope by calling PutObjectAcl on the key it is allowed to access. The handler authorizes the request against the requested nested key but then writes the updated entry back to the bucket root rather than the key's actual parent directory, so an ACL change on allowed/protected.txt is instead applied to protected.txt at the bucket root. Because the update carries the full entry rather than only ACL metadata, an existing target object is overwritten with the content, metadata, owner information, and ACL of the scoped object, bypassing the object-level action scoping configured through the static S3 identity file. 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":"weaponised"},"has_fix":true,"headline":"Missing authorization in seaweedfs","id":"CVE-2026-77611","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":1,"n_references":2,"next":{"headline":"Opencast: Session fixation in login enables account takeover via crafted link","id":"CVE-2026-77614"},"packages":[{"ecosystem":"Bitnami","fixed":["4.40.0"],"introduced":["0"],"last_affected":[],"package":"seaweedfs","purl":"pkg:bitnami/seaweedfs","source":"BIT-seaweedfs-2026-77611"}],"prev":{"headline":"Semantic MediaWiki has a query debug output XSS (`DebugFormatter`)","id":"CVE-2026-77610"},"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-27","vendors":["seaweedfs"]},"summary":"Authenticated users can bypass object-scope restrictions to overwrite unrelated files at the bucket root via PutObjectAcl.","url":"https://insights.sbomify.com/CVE-2026-77611/"}