IBM Langflow OSS CVE-2026-110200

Requires an authenticated account on the Langflow OSS instance (CVSS PR:L), so exploitation is limited to users who already have valid low-privilege credentials - it is not remote-unauthenticated. The description attributes the exposure to cleartext storage of sensitive information (CWE-312) but does not name the exact feature, field, configuration setting, or storage backend involved, so the specific data exposed and the precise trigger are not described in the available sources. Limiting factors: the authentication requirement and confidentiality-only impact (no integrity/availability effect) constrain real-world risk; affected scope is Langflow OSS versions 1.0.0 through 1.12.4.

This is a moderate-severity information disclosure flaw (CVSS 6.5, CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) with a confidentiality-only impact and no effect on integrity or availability. The CVSS vector indicates network-reachable, low-complexity exploitation but requires low-level privileges (PR:L), meaning the attacker must already be an authenticated user of the Langflow OSS instance - this is not a pre-auth exposure. There is no EPSS score, no CISA KEV listing, and no public proof-of-concept provided in the input, so there is no evidence of active exploitation or weaponization; the vuln.today decision label is 'this_month', indicating routine-but-not-emergency patch urgency rather than act_now/emergency. The signals are internally consistent: a confirmed vendor patch exists, but the absence of KEV/EPSS/POC combined with the authenticated-access requirement points to this being a real-but-contained issue rather than a high-urgency internet-wide threat. The CWE-312 (cleartext storage) class means the sensitive data is exposed at rest, so the practical risk depends heavily on what is stored (e.g., API keys, credentials, connection secrets) and which authenticated roles can reach it - details the available sources do not specify.

An authenticated user of an IBM Langflow OSS instance (versions 1.0.0 through 1.12.4) accesses sensitive information - such as stored secrets or credentials - that the application retains in cleartext rather than encrypting. Because the CVSS vector is AV:N/PR:L, a low-privileged remote account is sufficient to read the exposed data, but no pre-authentication or user-interaction path is indicated. No public exploit code is identified in the available data, and the exact storage location and data type are not described in the sources.