CVE-2026-127214

waiting for further signalsZero needs more public information before it can validate it.

GHSA-vqvj-w792-h4m6 ↗EUVD-2026-125728 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
FlowiseAI Flowise <= 3.1.4
ETK-2026-4435Zero's internal tracking ID, independent of the CVE number., permanent identifier
8h 25msince last run
26mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+3h58m
0
+2h
+6h
+8h
+10h
+12h

description

Flowise through version 3.1.4 is affected by a server-side request forgery weakness in its Custom Function sandbox. An authenticated user with chatflow or agentflow create or update permissions may cause the Flowise server to contact internal, loopback, or cloud metadata services.

mitigation

Restrict Custom Function use and remove chatflow or agentflow create/update permissions from untrusted accounts. Apply outbound network controls so the Flowise service cannot reach internal management endpoints, loopback services, or cloud metadata addresses.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
26m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-13 19:27Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-13 19:27Z
    ghsa: trigger signal, started the run
  2. 2026-11-13 19:27Z

this entry in the feed

GET /api/v1/feed/CVE-2026-127214

{
  "etk_id": "ETK-2026-4435",
  "cve_id": "CVE-2026-127214",
  "display_id": "CVE-2026-127214",
  "ghsa_id": "GHSA-vqvj-w792-h4m6",
  "euvd_id": "EUVD-2026-125728",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Server-side request forgery in Flowise Custom Function sandbox",
  "summary": "Flowise through version 3.1.4 is affected by a server-side request forgery weakness in its Custom Function sandbox. An authenticated user with chatflow or agentflow create or update permissions may cause the Flowise server to contact internal, loopback, or cloud metadata services.",
  "mitigation": "Restrict Custom Function use and remove chatflow or agentflow create/update permissions from untrusted accounts. Apply outbound network controls so the Flowise service cannot reach internal management endpoints, loopback services, or cloud metadata addresses.",
  "vendor": "FlowiseAI",
  "product": "Flowise",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 3.1.4"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Flowise",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 25.8011544,
  "t0_at": "2026-11-13T19:27:24.723000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-13T19:27:24.723000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-13T19:27:24.723000+00:00",
      "url": "https://github.com/advisories/GHSA-vqvj-w792-h4m6"
    }
  }
}

published 2026-11-13 22:59Z
last change 2026-11-14 07:07Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.