langflow-ai langflow up to 1.8.3 Project Creation Endpoint projects.py create_project/encrypt_auth_settings cleartext storage in file
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.9 | $0-$5k | 3.00 |
Summary
A vulnerability, which was classified as problematic, has been found in langflow-ai langflow up to 1.8.3. The impacted element is the function create_project/encrypt_auth_settings of the file src/backend/base/Langflow/api/v1/projects.py of the component Project Creation Endpoint. Performing a manipulation of the argument auth_settings results in cleartext storage in file.
This vulnerability was named CVE-2026-6598. The attack may be initiated remotely. In addition, an exploit is available.
The vendor was contacted early about this disclosure but did not respond in any way.
Details
A vulnerability was found in langflow-ai langflow up to 1.8.3. It has been classified as problematic. This affects the function create_project/encrypt_auth_settings of the file src/backend/base/Langflow/api/v1/projects.py of the component Project Creation Endpoint. The manipulation of the argument auth_settings with an unknown input leads to a cleartext storage in file vulnerability. CWE is classifying the issue as CWE-313. The product stores sensitive information in cleartext in a file, or on disk. This is going to have an impact on confidentiality.
The advisory is shared at gist.github.com. This vulnerability is uniquely identified as CVE-2026-6598. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1555 for this issue.
The exploit is shared for download at gist.github.com. It is declared as proof-of-concept. The vendor was contacted early about this disclosure but did not respond in any way.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 3.9
VulDB Base Score: 4.3
VulDB Temp Score: 3.9
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Cleartext storage in fileCWE: CWE-313 / CWE-312 / CWE-310
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
04/19/2026 Advisory disclosed04/19/2026 VulDB entry created
04/19/2026 VulDB entry last update
Sources
Advisory: gist.github.comStatus: Not defined
CVE: CVE-2026-6598 (🔒)
GCVE (CVE): GCVE-0-2026-6598
GCVE (VulDB): GCVE-100-358233
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 04/19/2026 15:52Changes: 04/19/2026 15:52 (59)
Complete: 🔍
Submitter: Eric-f
Cache ID: 216::103
Submit
Accepted
- Submit #791921: Langflow <= 1.8.3 CWE-311: Missing Encryption of Sensitive Data (by Eric-f)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.