CVE-2026-69258Public exploitNetwork attack vectorHinoki check available

Unauthenticated flow-context injection via ungated configuration spread

Published Aug 4, 2026 · Updated Aug 4, 2026

Property injection in Flowise before 3.1.3 allows remote attackers to alter public chatflow execution via crafted prediction requests. The prediction endpoint spreads attacker-controlled overrideConfig properties into flowConfig and flowData without enforcing apiOverrideStatus, overwriting session identifiers, history, and values resolved through $flow.* templates. Exploitation requires a public chatflow and its identifier; conversation memory or security-sensitive template use determines whether injected values expose prior chats, corrupt sessions, or influence downstream nodes.

CVSS severity8.8
High
EPSS probability0.45%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Property injection in Flowise before 3.1.3 allows remote attackers to alter public chatflow execution via crafted prediction requests. The prediction endpoint spreads attacker-controlled overrideConfig properties into flowConfig and flowData without enforcing apiOverrideStatus, overwriting session identifiers, history, and values resolved through $flow.* templates. Exploitation requires a public chatflow and its identifier; conversation memory or security-sensitive template use determines whether injected values expose prior chats, corrupt sessions, or influence downstream nodes.

The record

CVE
CVE-2026-69258
Published
Aug 4, 2026
Updated
Aug 4, 2026
Vendor
FlowiseAI
Product
Flowise
Classifications
CWE-639, CWE-915, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 4, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 4, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 3.1.3

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

FlowiseAI · Flowiseversion=< 3.1.3

Published CVSS scores

8.8GitHubCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-639Authorization Bypass Through User-Controlled Key
CWE-915Improperly Controlled Modification of Dynamically-Determined Object Attributes
T1190Exploit Public-Facing Application

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo