CVE-2026-6598
Received Received - Intake
Cleartext Storage Vulnerability in Langflow Project Creation Endpoint

Publication date: 2026-04-20

Last updated on: 2026-04-29

Assigner: VulDB

Description
A security vulnerability has been detected in langflow-ai langflow up to 1.8.3. The affected 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. Such manipulation of the argument auth_settings leads to cleartext storage in a file or on disk. The attack can be launched remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-20
Last Modified
2026-04-29
Generated
2026-05-06
AI Q&A
2026-04-20
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
langflow-ai langflow to 1.8.3 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-312 The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.
CWE-313 The product stores sensitive information in cleartext in a file, or on disk.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability exists in the langflow-ai langflow software up to version 1.8.3, specifically in the function create_project/encrypt_auth_settings within the Project Creation Endpoint component. The issue arises because the argument auth_settings is manipulated in a way that causes sensitive authentication settings to be stored in cleartext on disk or in a file. This means that confidential information is not properly encrypted and can be accessed by unauthorized parties.

The vulnerability can be exploited remotely, allowing attackers to potentially access sensitive authentication data without needing physical access to the system.


How can this vulnerability impact me? :

The impact of this vulnerability is that sensitive authentication settings may be exposed in cleartext, which can lead to unauthorized access to systems or data. Attackers exploiting this vulnerability could gain access to authentication credentials or other sensitive information stored by the application, potentially compromising the security of the affected system.

Since the exploit can be launched remotely, it increases the risk of unauthorized access without physical presence, making it easier for attackers to compromise the system.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

This vulnerability involves the cleartext storage of authentication settings on disk, which can lead to unauthorized access to sensitive information if exploited.

Such insecure handling of authentication data may impact compliance with standards and regulations like GDPR and HIPAA, which require protection of sensitive data and proper security controls to prevent unauthorized access.

However, specific impacts on compliance are not detailed in the provided information.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by inspecting the stored project data for plaintext sensitive authentication credentials, especially in the auth_settings field. Since the vulnerability involves cleartext storage of sensitive fields like passwords or secret tokens, you can query the project retrieval API endpoint to check if such fields are returned unencrypted.

A practical approach is to create a project with known sensitive auth_settings (e.g., a password) and then retrieve the project data via the API to see if the sensitive data is stored and returned in plaintext.

Example commands to detect the vulnerability might include:

  • Use curl or similar tools to create a project with sensitive auth_settings, e.g.: curl -X POST http://<langflow-host>/api/v1/projects -H 'Content-Type: application/json' -d '{"auth_settings": {"db_password": "SECRET123"}, "other_project_data": "..."}'
  • Retrieve the project data and check if the sensitive field is returned in plaintext: curl http://<langflow-host>/api/v1/projects/<project_id>

If the sensitive fields like db_password appear unencrypted in the response, the vulnerability is present.


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include avoiding the storage of sensitive authentication credentials in the vulnerable versions of Langflow, especially in the auth_settings field.

Since the vulnerability arises from incomplete encryption of sensitive fields, you should:

  • Avoid using or storing sensitive fields that are not covered by the encryption allowlist (e.g., passwords, secret tokens) until a patch or update is available.
  • Restrict access to the Langflow database and API endpoints to trusted and authenticated users only, minimizing exposure risk.
  • Monitor for updates or patches from the vendor or community that address the encryption shortcomings and apply them as soon as they become available.

If possible, consider encrypting sensitive data before submitting it to the Langflow system as a temporary workaround.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart