{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-55418 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-55418 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-55418 is a high-severity missing authorization vulnerability in labring FastGPT, published on 7 Jul 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-55418 and fix it if it is affected.\n\nWhat it is: CVE-2026-55418 is a high-severity missing authorization vulnerability in labring FastGPT, published on 7 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-55418 in the wild and no public exploit code.\n\nAffected product: labring FastGPT. 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-55418/ (Markdown: https://insights.sbomify.com/CVE-2026-55418/index.md)","id":"CVE-2026-55418","markdown":"https://insights.sbomify.com/CVE-2026-55418/index.md","name":"CVE-2026-55418","record":{"aliases":["GHSA-6rxv-p43w-mmx5"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"AI knowledge base platform","requires_auth":"none","summary":"Attackers can access other teams' files by manipulating S3 object keys in presign or preview requests, leading to cross-team data disclosure.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"FastGPT is an open source AI knowledge base platform. Prior to v4.15.0-beta5, two FastGPT file handlers authorize an unrelated resource and then sign or read an S3 object using a key taken directly from the request, without checking that the key belongs to the caller's team. Because S3 object keys are global within the bucket and carry the tenant id only as a path segment, an attacker can supply another team's key and obtain its file contents through the chat-file presign endpoint or dataset preview endpoint. This issue is fixed in version v4.15.0-beta5.","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":"FastGPT: S3 presign/read handlers do not bind the object key to the caller's team (cross-team file disclosure)","id":"CVE-2026-55418","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Reachy Mini: Unrestricted Upload of File with Dangerous Type","id":"CVE-2026-55419"},"packages":[],"prev":{"headline":"Chevereto private profile setting leaks username on /json endpoint","id":"CVE-2026-55417"},"products":["FastGPT"],"published":"2026-07-07","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-09","vendors":["labring"]},"summary":"Attackers can access other teams' files by manipulating S3 object keys in presign or preview requests, leading to cross-team data disclosure.","url":"https://insights.sbomify.com/CVE-2026-55418/"}