What is the CVSS score of EUVD-2026-45330?

EUVD-2026-45330 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.2%.

Which versions of IBM Langflow are affected by EUVD-2026-45330?

IBM Langflow OSS versions 1.0.0 through 1.10.1 contain hard-coded authentication credentials embedded in every deployment, enabling remote attackers to bypass authentication and achieve full data…. A patch is available.

How to fix or mitigate EUVD-2026-45330?

Within 24 hours, conduct a complete inventory of IBM Langflow OSS deployments across your infrastructure and identify any instances running versions 1.0.0 through 1.10.1; prioritize identifying instances exposed to untrusted networks. Within 7 days, apply the available vendor patch to all affected instances, beginning with production environments and proceeding through development and testing. Within 30 days, complete patching of all remaining instances, conduct cryptographic rotation of any credentials or secrets managed through affected Langflow instances, and review access logs for signs of unauthorized access during the exposure window.

IBM Langflow EUVD-2026-45330

| CVE-2026-13446 CRITICAL

Use of Hard-coded Credentials (CWE-798)

2026-07-17 ibm

GHSA-m65w-r8pm-j2p4

IBM Authentication Bypass Langflow Oss

9.8

CVSS 3.1 · Vendor: ibm

Severity by source

Vendor (ibm) PRIMARY

9.8 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

vuln.today AI

9.8 CRITICAL

Static secret shipped in the software is remotely usable with no auth or user interaction (AV:N/AC:L/PR:N/UI:N); worst-case inbound-auth use yields full C/I/A loss.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (ibm).

CVSS VectorVendor: ibm

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 17, 2026 - 21:16 vuln.today

CVE Published

Jul 17, 2026 - 20:43 cve.org

CRITICAL 9.8

DescriptionCVE.org

IBM Langflow OSS 1.0.0 through 1.10.1 contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data.

AnalysisAI

Authentication bypass and full data compromise affects IBM Langflow OSS 1.0.0 through 1.10.1, which ships hard-coded credentials (a static password or cryptographic key) embedded in the application. Because the same secret is present in every deployment, remote attackers who read it from the public source or a binary can authenticate to inbound interfaces, impersonate the app to external components, or decrypt internal data on any affected instance. No public exploit identified at time of analysis, but the shared-secret nature makes exploitation trivial once the value is known.

Technical ContextAI

Langflow is a widely used open-source, low-code visual builder for LLM and AI-agent workflows, maintained under IBM. The root cause is CWE-798 (Use of Hard-coded Credentials): a secret is compiled into the codebase rather than generated per install or supplied via configuration. Per the description the secret serves one or more security-critical roles - inbound authentication (gating access to the app), outbound communication to external components (service/API authentication), or encryption of internal data (a static key that makes stored secrets recoverable). The affected package is identified by CPE cpe:2.3:a:ibm:langflow_oss across all versions in the 1.0.0-1.10.1 range. Hard-coded secrets in open-source projects are especially dangerous because the value is publicly auditable in the repository, eliminating any discovery or brute-force barrier.

RemediationAI

Patch available per vendor advisory - apply the fixed IBM Langflow OSS release referenced in IBM's bulletin at https://www.ibm.com/support/pages/node/7279991 (the exact fixed version was not included in the source data and should be confirmed there). Because the flaw is a static shared secret, upgrading alone is insufficient if the old credential stays valid: after patching, rotate or regenerate any keys, passwords, and encryption material tied to the deployment, and re-encrypt any internally stored secrets that may have been protected with the hard-coded key. As interim compensating controls until patched, restrict network access to the Langflow interface behind a VPN or IP allowlist and place it behind an authenticating reverse proxy, and isolate the external components it communicates with; the trade-off is reduced accessibility for legitimate remote users and added operational overhead. Do not expose Langflow directly to the internet.