CVE-2026-12763: Langflow is vulnerable to authentication bypass and insufficient session expiration
Noroxi assessment
Priority: Monitor (action score 16/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- According to the record, no fixed version is available yet.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
IBM Langflow OSS 1.0.0 through 1.11.5 could allow an authenticated attacker to access another user's MCP server context due to improper cache key isolation in the MCP Tools component.
- Published
- Sep 14, 2026
- Updated
- Nov 3, 2026
- EPSS
- 0.1% · 8th percentile
- CWE
- CWE-306
Report tools
Action score
16
Low priority for now.
- CVSS
- 16 / 40 · 4.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · ibm
- 4.2
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| langflow | langflow | cpe:2.3:a:langflow:langflow |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (ibm). Independent of NVD's CPE analysis and usually ahead of it.
IBM Langflow OSS
- 1.0.0 and later · up to and including 1.11.5affected · semver
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- langflow langflow1.0.0 and later · before 1.11.6
Same product
langflow: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-3248Langflow < 1.3.0 Unauthenticated RCE via /api/v1/validate/codeKEV99Now
- CVE-2026-33017Langflow has Unauthenticated Remote Code Execution via Public Flow Build EndpointKEV96Now
- CVE-2025-34291Langflow <= 1.6.9 CORS Misconfiguration to Token Hijack & RCEKEV95Now
Published before and after this one in the same product
- ← EarlierCVE-2026-84889Sep 10, 2026 · A path traversal vulnerability in file handling components could allow an authenticated attacker to write files to arbitrary locations on the server filesystem35Monitor
- ← EarlierCVE-2026-17628Sep 14, 2026 · Langflow is affected by improper authentication due to missing password verification in the password reset endpoint21Monitor
- Later →CVE-2026-12765Sep 14, 2026 · Langflow OSS is affected by server-side request forgery due to missing URL validation in flow components26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-3248525 days apartLangflow < 1.3.0 Unauthenticated RCE via /api/v1/validate/codeKEV99Now
- CVE-2026-21445255 days apartLangflow Missing Authentication on Critical API Endpoints45Plan
- CVE-2026-910359 days apartUnauthenticated Superuser Token Issuance via Auto-Login Endpoint40Plan
- CVE-2026-920259 days apartUnauthenticated User Registration Could Lead to Remote Code Execution39Monitor
- CVE-2026-850559 days apartAuthentication Bypass in Webhook Endpoints Allowed Unauthorized Flow Execution39Monitor
- CVE-2026-1987526 days apartUnauthenticated Registration POST Endpoint Permits Admin Email Overwrite and Outbound Relay Abuse in Langflow30Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2026-129440 days apartIncomplete Security Scanner Blocklist Enables Network-Based Code Execution38Monitor
- CVE-2026-785754 days apartLangflow is vulnerable to arbitrary code execution due to multiple incomplete code security controls and missing execution guards35Monitor
- CVE-2026-848894 days apartA path traversal vulnerability in file handling components could allow an authenticated attacker to write files to arbitrary locations on the server filesystem35Monitor
- CVE-2026-127660 days apartLangflow is vulnerable to Server-Side Request Forgery due to missing or bypassable URL validation in multiple components21Monitor
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1095 · Sep 15, 2026(IBM Çoklu Ürün Güvenlik Bildirimi)
Not on record for this CVE: patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-306 · Missing Authentication for Critical FunctionCVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
nvd-secondary
Root cause
A function added for development or support ships to production without authentication. It often relies on the assumption that it is “only reachable from the internal network.”
The bug in code
The whole CWE-306 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
// Added for the support team
app.post("/maintenance/reset", resetDevice);Fixed
if (config.maintenanceEnabled) {
app.post(
"/maintenance/reset",
requireSession, requireRole("admin"), resetDevice
);
}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.