{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-75898 exists.","fix":"No fix has been published for CVE-2026-75898 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-75898 is a high-severity server-side request forgery vulnerability in infiniflow ragflow, published on 18 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-75898 and fix it if it is affected.\n\nWhat it is: CVE-2026-75898 is a high-severity server-side request forgery vulnerability in infiniflow ragflow, published on 18 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-75898 exists.\n\nAffected product: infiniflow ragflow. 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-75898/ (Markdown: https://insights.sbomify.com/CVE-2026-75898/index.md)","id":"CVE-2026-75898","markdown":"https://insights.sbomify.com/CVE-2026-75898/index.md","name":"CVE-2026-75898","record":{"aliases":["GHSA-9m4v-54qq-67fw"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"RAGFlow AI platform","requires_auth":"low_privilege","summary":"Attackers can exploit an SSRF flaw in RAGFlow's agent invoke component to access internal network resources and cloud metadata endpoints.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"RAGFlow before 0.26.3 contains a server-side request forgery vulnerability in the agent workflow \"Invoke\" component (agent/component/invoke.py). The component builds an outbound request URL from canvas configuration and runtime template variables and passes it to requests.get, requests.post, or requests.put without calling the shared assert_url_is_safe validator or pinning the resolved address, unlike the crawler, SearXNG, file-upload, and RSS fetch paths. A user who can create or trigger an agent can direct the server to fetch loopback, link-local, and RFC 1918 destinations, including cloud instance metadata endpoints and services co-located on the deployment network, and the response body is returned as the component output. Where an agent is configured to interpolate the chat query into the Invoke URL, the destination is chosen by whoever can send that query.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-08-26","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-08-26T23:55:26Z","kind":"github_poc","ref":"https://github.com/t3bik/CVE-2026-75898","stars":0,"title":null}],"tier":"weaponised"},"has_fix":false,"headline":"RAGFlow \u003c 0.26.3 - Server-Side Request Forgery via Agent Invoke Component","id":"CVE-2026-75898","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"fast-uri vulnerable to server-side request forgery via repeated hostname percent-decoding","id":"CVE-2026-75899"},"packages":[],"prev":{"headline":"Uncontrolled Resource Consumption in Capabilities Route in OpenSearch Dashboards","id":"CVE-2026-75897"},"products":["ragflow"],"published":"2026-08-18","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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-24","vendors":["infiniflow"]},"summary":"Attackers can exploit an SSRF flaw in RAGFlow's agent invoke component to access internal network resources and cloud metadata endpoints.","url":"https://insights.sbomify.com/CVE-2026-75898/"}