CVE-2026-32311

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.5% (43rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated

Also known asEUVD-2026-23946 (ENISA EUVD)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
43rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 20, 2026

Last Modified

October 26, 2026

Advisory Details (2)

Auto-updated Nov 2, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Command Injection and Docker container escape allows root on host machine · Advisory · reconurge/flowsint · GitHub

https://github.com/reconurge/flowsint/security/advisories/GHSA-9g44-8xv2-f2m9
GitHub commit Patch Available

commit b52cbbb904c8 (reconurge/flowsint)

Patch available: reconurge/flowsint v1.0.0 (contains commit b52cbbb904c8)

https://github.com/reconurge/flowsint/commit/b52cbbb904c8013b74308d58af88bc7dbb1b055c

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 31× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 267 rows on record for this CVE, as 98 entries (2 repeats merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 167 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:52 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  2. 2026-11-12 22:25 UTCEchelonGraph re-scored
  3. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  4. 2026-11-11 22:51 UTCEchelonGraph re-scored
  5. 2026-11-11 16:39 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  6. 2026-11-10 23:44 UTCEchelonGraph re-scored
  7. 2026-11-10 16:43 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  8. 2026-11-10 00:37 UTCEchelonGraph re-scored
  9. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  10. 2026-11-09 01:30 UTCEchelonGraph re-scored
  11. 2026-11-08 16:39 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  12. 2026-11-08 02:24 UTCEchelonGraph re-scored
  13. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  14. 2026-11-07 03:17 UTCEchelonGraph re-scored
  15. 2026-11-06 16:37 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  16. 2026-11-06 05:55 UTCOSV refresh
  17. 2026-11-06 04:11 UTCEchelonGraph re-scored
  18. 2026-11-05 16:37 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  19. 2026-11-05 04:59 UTCEchelonGraph re-scored
  20. 2026-11-04 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  21. 2026-11-04 05:52 UTCEchelonGraph re-scored
  22. 2026-11-03 16:47 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  23. 2026-11-03 06:44 UTCEchelonGraph re-scored
  24. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  25. 2026-11-02 07:38 UTCEchelonGraph re-scored
Show 73 more
  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  2. 2026-11-01 08:31 UTCEchelonGraph re-scored
  3. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  4. 2026-10-31 09:24 UTCEchelonGraph re-scored
  5. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  6. 2026-10-30 10:16 UTCEchelonGraph re-scored
  7. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  8. 2026-10-29 11:09 UTCEchelonGraph re-scored
  9. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  10. 2026-10-28 11:57 UTCEchelonGraph re-scored
  11. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  12. 2026-10-26 22:27 UTCEchelonGraph re-scored
  13. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  14. 2026-10-26 09:10 UTCEchelonGraph re-scored
  15. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  16. 2026-10-25 14:35 UTCEchelonGraph re-scored
  17. 2026-10-25 10:01 UTCEchelonGraph re-scored
  18. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  19. 2026-10-24 10:54 UTCEchelonGraph re-scored
  20. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  21. 2026-10-23 11:45 UTCEchelonGraph re-scored
  22. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  23. 2026-10-22 12:35 UTCEchelonGraph re-scored
  24. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  25. 2026-10-21 13:29 UTCEchelonGraph re-scored
  26. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  27. 2026-10-20 14:22 UTCEchelonGraph re-scored
  28. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  29. 2026-10-19 13:23 UTCEchelonGraph re-scored
  30. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  31. 2026-10-18 03:47 UTCEchelonGraph re-scored
  32. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  33. 2026-10-17 13:49 UTCEchelonGraph re-scored
  34. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  35. 2026-10-16 14:40 UTCEchelonGraph re-scored
  36. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  37. 2026-10-15 15:33 UTCEchelonGraph re-scored
  38. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  39. 2026-10-14 09:50 UTCEchelonGraph re-scored
  40. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  41. 2026-10-13 07:44 UTCEchelonGraph re-scored
  42. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  43. 2026-10-12 16:14 UTCEchelonGraph re-scored
  44. 2026-10-11 19:56 UTCEchelonGraph re-scored
  45. 2026-10-11 17:10 UTCEchelonGraph re-scored
  46. 2026-10-11 14:38 UTCEchelonGraph re-scored
  47. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  48. 2026-10-11 06:55 UTCOSV refresh
  49. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  50. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  51. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  52. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  53. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  54. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  55. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  56. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  57. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  58. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  59. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  60. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  61. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  62. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  63. 2026-09-21 19:19 UTCOSV refresh
  64. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  65. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  66. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  67. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  68. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  69. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  70. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  71. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  72. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  73. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.5% · 41st percentile

Frequently asked(5)

What is CVE-2026-32311?
CVE-2026-32311 is a critical-severity vulnerability; its CVE record was published on April 20, 2026. 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…
When was the CVE record for CVE-2026-32311 published?
The CVE record for CVE-2026-32311 was published on April 20, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 26, 2026; the record at its source may have been updated since.
Is CVE-2026-32311 actively exploited?
CVE-2026-32311 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-32311?
CVE-2026-32311 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-32311?
A fix for CVE-2026-32311 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-32311

Explore →

Is Your Infrastructure Affected by CVE-2026-32311?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.