dbcve.org
FlowsintApplication

CVE-2026-32311

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-20
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Flowsint is an open-source OSINT graph exploration tool designed for cybersecurity investigation, transparency, and verification. Flowsint allows a user to create investigations, which are used to manage sketches and analyses. Sketches have controllable graphs, which are comprised of nodes and relationships. The sketches contain information on an OSINT target (usernames, websites, etc) within these nodes and relationships. The nodes can have automated processes execute on them called 'transformers'. A remote attacker can create a sketch, then trigger the 'org_to_asn' transform on an organization node to execute arbitrary OS commands as root on the host machine via shell metacharacters and a docker container escape. Commit b52cbbb904c8013b74308d58af88bc7dbb1b055c appears to remove the code that causes this issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Flowsint OSINT tool contains a command injection vulnerability in the 'org_to_asn' transformer. Attackers can create a sketch, then trigger this transform on an organization node to execute arbitrary OS commands as root via shell metacharacters, with the additional capability to escape the Docker container.

MitigationApply the patch from commit b52cbbb904c8013b74308d58af88bc7dbb1b055c which removes the vulnerable code, or update to the patched version of Flowsint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FlowsintApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Flowsint installation
    Check for Flowsint binary or service running on the system using 'ps aux | grep -i flowsint' or check for flowsint installation directory
    Affected if Flowsint is installed or running on the host
  2. Identify org_to_asn transformer
    Search the Flowsint codebase for 'org_to_asn' transformer file or module definition, typically in transformers configuration or source code
    Affected if The org_to_asn transformer exists in the Flowsint installation
  3. Verify sketch creation permissions
    Check Flowsint access control configuration for user roles permitted to create sketches, typically found in configuration files or user management settings
    Affected if Untrusted or unauthenticated users are allowed to create sketches
  4. Inspect org_to_asn transformer code
    Examine the org_to_asn transformer source code for shell execution patterns (subprocess, os.system, shell=True) that accept user input without sanitization
    Affected if The transformer code contains unsanitized command execution functions processing organization input
  5. Check for patch commit
    If using git, run 'git log --oneline --all | grep b52cbbb' to verify the security patch commit removing the vulnerable code is applied
    Affected if The commit b52cbbb904c8013b74308d58af88bc7dbb1b055c is NOT present in the git history

A user is affected if Flowsint is installed with the org_to_asn transformer present and sketch creation is available to untrusted or unauthenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Apply the patch from commit b52cbbb904c8013b74308d58af88bc7dbb1b055c which removes the vulnerable code, or update to the patched version of Flowsint.

Recommended fix Moderate confidence

Commit b52cbbb904c8013b74308d58af88bc7dbb1b055c or later

  1. 1. Identify the current Flowsint installation location
  2. 2. Navigate to the Flowsint repository or installation directory
  3. 3. Pull or checkout the fixed commit: b52cbbb904c8013b74308d58af88bc7dbb1b055c
  4. 4. Verify the 'org_to_asn' transformer code has been modified to remove command injection vulnerability
  5. 5. Rebuild and redeploy the application
  6. 6. Test that the org_to_asn transform no longer accepts shell metacharacters
  7. 7. Verify the Docker container escape vector has been addressed
  8. 8. Monitor for any unexpected behavior in investigation/sketch functionality
Caveat Unknown; command injection fixes typically do not introduce functional breaking changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Flowsint Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32311 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32311 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data