CVE-2026-56270Known exploitationPublic exploitNetwork attack vector

Unauthenticated OAuth secret disclosure via loginmethod endpoint

Published Jun 24, 2026 · Updated Jun 24, 2026

Missing authentication in Flowise before 3.1.0 allows remote attackers to read OAuth client secrets through /api/v1/loginmethod. The endpoint accepts an organizationId in an unauthenticated GET request and returns the matching SSO provider configuration with clientSecret values in cleartext. Exposure requires a reachable endpoint and a valid organization identifier; it discloses integration credentials without directly writing configuration.

CVSS severity7.5
High
EPSS probability2.05%
Next 30 days · Sep 16, 2026
Known exploitationReported
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Missing authentication in Flowise before 3.1.0 allows remote attackers to read OAuth client secrets through /api/v1/loginmethod. The endpoint accepts an organizationId in an unauthenticated GET request and returns the matching SSO provider configuration with clientSecret values in cleartext. Exposure requires a reachable endpoint and a valid organization identifier; it discloses integration credentials without directly writing configuration.

The record

CVE
CVE-2026-56270
Published
Jun 24, 2026
Updated
Jun 24, 2026
Vendor
FlowiseAI
Product
Flowise
Classifications
CWE-312, CWE-306, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jun 24, 2026CVE publishedPublication date reported by the CVE source.
  2. Jun 24, 2026Record updatedLatest update available in the CVE record.
  3. Jul 8, 2026Exploitation reportedPrevidian sensor-reported exploitation of CVE-2026-56270

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=0 <3.1.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

FlowiseAI · Flowiseversion=0 <3.1.0

Published CVSS scores

5.3GitHub Security AdvisoryCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
7.5VulnCheck CNACVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
8.7VulnCheck CNACVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/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 exploitationReported
Public exploitPublished

Weakness, pattern, technique

CWE-312Cleartext Storage of Sensitive Information
CWE-306Missing Authentication for Critical Function
T1190Exploit Public-Facing Application

Public exploit references

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

Reported exploitation

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