CVE-2025-34267

CRITICALNVD 9.99.9
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.9 under NVD CVSS v3. EPSS exploit probability: 6.9% (94th 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-2025-34455 (ENISA EUVD) · GHSA-r4hh-pcgx-j5r2 (GitHub Security Advisories)Source: ENISA EUVD

9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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: 6.9%CVSS: 9.9Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Flowise v3.0.1 < 3.0.8 and all versions after with 'ALLOW_BUILTIN_DEP' enabled contain an authenticated remote code execution vulnerability and node VM sandbox escape due to insecure use of integrated modules (Puppeteer and Playwright) within the nodevm execution environment. An authenticated attacker able to create or run a tool that leverages Puppeteer/Playwright can specify attacker-controlled browser binary paths and parameters. When the tool executes, the attacker-controlled executable/parameters are run on the host and circumvent the intended nodevm sandbox restrictions, resulting in execution of arbitrary code in the context of the host. This vulnerability was incorrectly assigned as a duplicate CVE-2025-26319 by the developers and should be considered distinct from that identifier.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
61
EG Risk 61/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)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 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.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.
EPSS PROB
6.9%
EPSS %ILE
94th
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.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 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
6.9% 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 or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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 or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

October 14, 2025

Last Modified

November 8, 2026

Advisory Details (3)

Auto-updated Nov 8, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr.
GitHub pull request Patch Available

Chore/Disable Available Dep By Default

Patch available: FlowiseAI/Flowise [email protected] (PR #5231 merged 2025-09-18)

https://github.com/FlowiseAI/Flowise/pull/5231
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Flowise Authenticated Command Execution and Sandbox Bypass via Puppeteer and Playwright Packages · Advisory · FlowiseAI/Flowise · GitHub

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-5w3r-f6gm-c25w
Web page

Flowise - Build AI Agents, Visually

https://flowiseai.com/

Vendor Advisories for CVE-2025-34267(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmflowise @ 3.0.8 (fixes >= 3.0.1, < 3.0.8)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
flowise—
  • 3.0.1 up to 3.0.8: fixed in 3.0.8
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 42× 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 241 rows on record for this CVE, as 99 entries (1 repeat 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 141 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2025-34267?
CVE-2025-34267 is a critical-severity vulnerability; its CVE record was published on October 14, 2025. Flowise v3.0.1 < 3.0.8 and all versions after with 'ALLOW_BUILTIN_DEP' enabled contain an authenticated remote code execution vulnerability and node VM sandbox escape due to insecure use of integrated modules (Puppeteer and Playwright) within the nodevm execution environment. An authenticated…
When was the CVE record for CVE-2025-34267 published?
The CVE record for CVE-2025-34267 was published on October 14, 2025. 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 November 8, 2026; the record at its source may have been updated since.
Is CVE-2025-34267 actively exploited?
CVE-2025-34267 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.9% probability of exploitation in the next 30 days (94th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-34267?
CVE-2025-34267 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2025-34267?
A fix for CVE-2025-34267 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-34267 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-34267

Explore →

Is Your Infrastructure Affected by CVE-2025-34267?

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

Book a Demo →Browse All CVEs