IBM Langflow OSS EUVD-2026-113132

Exploitation requires a valid authenticated account on the Langflow OSS instance (CVSS PR:L), reachable over the network (AV:N), with no user interaction needed. The affected versions are IBM Langflow OSS 1.0.0 through 1.12.8. The precise feature, endpoint, or configuration that exposes the credentials is not described in the available sources, so it cannot be stated which flows or settings are prerequisites. The main limiting factor is the authentication requirement - this is not exploitable by a fully unauthenticated attacker - which, combined with confidentiality-only impact (no integrity or availability effect), bounds realistic risk below that of a pre-auth flaw.

This is a moderate-severity information-disclosure issue (CVSS 6.5, CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) in IBM Langflow OSS. The vector indicates a network-reachable, low-complexity attack requiring low-level authenticated privileges (PR:L), no user interaction, with high confidentiality impact but no integrity or availability impact - consistent with CWE-522 (insufficiently protected credentials) leaking sensitive data to an already-authenticated user. The vendor-assigned priority is 'this_month' rather than an urgent tier, which aligns with the signal picture: no CISA KEV listing, no public exploit identified, and no EPSS probability supplied in the input. No signals are directly conflicting, but several are simply absent: EPSS is missing (so widespread-exploitation likelihood cannot be quantified) and no SSVC decision fields (automatable, technical impact) were provided, so the 'this_month' label is the primary prioritization signal. Net assessment: a real but not emergency-grade issue - the authentication requirement and confidentiality-only impact bound the risk, and with a patch available this is a routine-to-prompt remediation rather than a drop-everything event.

An attacker who already holds a low-privilege authenticated account on a Langflow OSS instance (or who obtains one) sends requests to the application and retrieves credentials or other sensitive data that the platform fails to protect adequately. Because the confidentiality impact is High, the exposed material could include stored secrets such as API keys or connection credentials used by flows. No public exploit code has been identified, so exploitation would require an attacker to independently identify the exposure.