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.
FlowIntel versions up to 3.3.0 can be tricked into making server-side HEAD requests to attacker-chosen URLs through external references. This can expose internal services reachable from the FlowIntel server, including restricted network locations. Public sources do not cite active exploitation.
Executive priority
Treat this as a moderate-priority update for affected FlowIntel systems. It is not reported as exploited, but SSRF can become high-impact when the server can reach sensitive internal services. Prioritize internet-facing or broadly accessible deployments.
Technical view
CVE-2026-9813 is a CWE-918 SSRF in app/case/task.py external reference URL probing. Insufficient URL scheme and resolved-address validation may permit requests to loopback, link-local, private, reserved, or other restricted destinations. CVSS 4.0 score is 6.2, medium severity.
Likely exposure
Exposure is likely limited to FlowIntel deployments at or below 3.3.0 where users can submit external reference URLs. Risk depends on server network reachability and whether internal services or metadata endpoints are accessible from the application host.
Exploitation context
The source bundle lists KEV as false and provides no cited evidence of active exploitation. The attack requires the ability to submit an external reference URL and appears constrained to server-issued HTTP HEAD probing, but impact can be serious in permissive internal networks.
Researcher notes
The affected metadata in the bundle is inconsistent, but the description clearly names FlowIntel up to 3.3.0 and a patch commit. Do not assume broader product impact or exploit availability beyond these sources.
Mitigation direction
Apply the referenced vendor patch commit or a vendor release containing it.
Check FlowIntel vendor guidance for any newer fixed version or deployment notes.
Restrict who can submit external reference URLs until patched.
Limit application egress to approved destinations where operationally possible.
Block application access to internal metadata and restricted network services.
Validation and detection
Inventory FlowIntel deployments and identify versions up to 3.3.0.
Confirm whether the referenced patch is present in deployed code.
Review external reference URL submission paths and access controls.
Check application and proxy logs for unusual HEAD requests from the server.
Verify egress controls prevent access to restricted internal destinations.
Based on public source material and reviewed before publication.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve
time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present,
the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-918 · source CWE mapping
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.