CVE-2026-56271

validatedZero produced an exploit or a check.

GHSA-jpvq-qwhh-pw47 ↗EUVD-2026-43228 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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.+71d
FlowiseAI Flowise <=3.0.13
fixed in 3.1.0
CWE-321 Use of Hard-coded Cryptographic Key
ETK-2026-31, permanent identifier
pkg:npm/flowise
+79dTTV
21mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
cve.org publicationtrigger signal +70dkev+71dcheck available+79dagent stopped
0
+20d
+40d
+60d

description

Flowise 3.0.13 and earlier may accept attacker-forged JWTs because its enterprise authentication middleware falls back to publicly known token secrets and validation values. An attacker can impersonate users, including administrators, when the JWT secret, audience, and issuer environment variables have not been explicitly configured.

mitigation

Upgrade Flowise to version 3.1.0 or later. Set unique values for JWT_AUTH_TOKEN_SECRET, JWT_REFRESH_TOKEN_SECRET, JWT_AUDIENCE, and JWT_ISSUER, and rotate existing authentication secrets.

fixed in 3.1.0

check
available
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.
deterministic
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.66%50th percentile
agent run time
21m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-07-12 12:06Z
Δ 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.
+71d

outcome

Check only, differential: the check fires on the vulnerable build and is silent on the patched one.

source signals

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

  1. 2026-07-12 12:06Z
  2. 2026-09-21
    vulncheck_kev: trigger signal, started the run
  3. 2026-09-21 00:00Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-31",
  "cve_id": "CVE-2026-56271",
  "display_id": "CVE-2026-56271",
  "ghsa_id": "GHSA-jpvq-qwhh-pw47",
  "euvd_id": "EUVD-2026-43228",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Hardcoded JWT defaults enable authentication bypass in Flowise",
  "summary": "Flowise 3.0.13 and earlier may accept attacker-forged JWTs because its enterprise authentication middleware falls back to publicly known token secrets and validation values. An attacker can impersonate users, including administrators, when the JWT secret, audience, and issuer environment variables have not been explicitly configured.",
  "mitigation": "Upgrade Flowise to version 3.1.0 or later. Set unique values for JWT_AUTH_TOKEN_SECRET, JWT_REFRESH_TOKEN_SECRET, JWT_AUDIENCE, and JWT_ISSUER, and rotate existing authentication secrets.",
  "vendor": "FlowiseAI",
  "product": "Flowise",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<=3.0.13"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "3.1.0"
      ],
      "package_name": "flowise",
      "purl": "pkg:npm/flowise"
    }
  ],
  "cwes": [
    321
  ],
  "cvss_score": 9.8,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0066,
  "epss_percentile": 0.5047,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 21.255270733333333,
  "t0_at": "2026-07-12T12:06:32.246000+00:00",
  "signals": {
    "check": {
      "at": "2026-09-29T23:10:57.634043+00:00",
      "days": 79.46140495420138,
      "is_lower_bound": false,
      "measured_at": "2026-07-12T12:06:32.246000+00:00",
      "url": null
    },
    "kev": {
      "at": "2026-09-21T00:00:00+00:00",
      "days": 71,
      "is_lower_bound": false,
      "measured_at": "2026-07-12T12:06:32.246000+00:00",
      "precision": "day",
      "url": "https://vulncheck.com/cve/CVE-2026-56271"
    },
    "trigger_signal": {
      "at": "2026-09-21T00:00:00+00:00",
      "days": 70.49546011574074,
      "is_lower_bound": false,
      "measured_at": "2026-07-12T12:06:32.246000+00:00",
      "url": "https://vulncheck.com/cve/CVE-2026-56271"
    }
  }
}

published 2026-09-29 22:49Z
last change 2026-10-21 05:00Z

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.