{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-9813 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-9813 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-9813 is a medium-severity server-side request forgery vulnerability in flowintel, published on 28 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-9813 and fix it if it is affected.\n\nWhat it is: CVE-2026-9813 is a medium-severity server-side request forgery vulnerability in flowintel, published on 28 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-9813 in the wild and no public exploit code.\n\nAffected product: flowintel. 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-9813/ (Markdown: https://insights.sbomify.com/CVE-2026-9813/index.md)","id":"CVE-2026-9813","markdown":"https://insights.sbomify.com/CVE-2026-9813/index.md","name":"CVE-2026-9813","record":{"aliases":["GHSA-58wp-jwch-fgj5"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"FlowIntel application","requires_auth":"low_privilege","summary":"Attackers can exploit SSRF in FlowIntel to force the server to access internal network resources or cloud metadata endpoints.","user_interaction":"required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CIRCL","cpe":[{"product":"flowintel","vendor":"flowintel"}],"cvss":{"score":6.2,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:L/VI:N/VA:N/SC:L/SI:H/SA:H/S:N/RE:L/U:Green","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"FlowIntel up to version 3.3.0 contains a server-side request forgery (SSRF) vulnerability in the external reference URL probe functionality in app/case/task.py. An attacker who can submit an external reference URL can cause the application server to issue an HTTP HEAD request to an attacker-specified destination. Due to insufficient validation of the URL scheme and resolved destination address, affected versions may allow requests to loopback, link-local, private, reserved, or other restricted network resources, potentially enabling interaction with internal services or cloud metadata endpoints from the server's network context.","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":"FlowIntel external reference URL probe allows server-side request forgery","id":"CVE-2026-9813","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"An OS command injection vulnerability exists in the boa formWizard newPass functionality of X2000R (version(s): TOTOLINK-X2000R-Gh-V1.0.0-B20250421.1327).","id":"CVE-2026-9814"},"packages":[],"prev":{"headline":"Missing property field ownership validation in Playbooks run property update endpoint","id":"CVE-2026-9812"},"products":["flowintel"],"published":"2026-05-28","related":[],"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)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-28","vendors":["flowintel"]},"summary":"Attackers can exploit SSRF in FlowIntel to force the server to access internal network resources or cloud metadata endpoints.","url":"https://insights.sbomify.com/CVE-2026-9813/"}