Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-13446 – Hard-Coded Credentials Enabling Unauthorized Superuser Access – IBM Langflow OSS…

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-13446 is a critical (CVSS 9.8) hard-coded credentials vulnerability (CWE-798) in IBM Langflow OSS, affecting all releases from version 1.0.0 through 1.10.1. The application enforces hardcoded default superuser credentials at startup regardless of any operator-supplied environment variable overrides, allowing a remote unauthenticated attacker with knowledge of those credentials to gain full superuser access to the platform. IBM has released a patch in version 1.10.2.

Technical details

  • Root cause: The application contains hard-coded default superuser credentials (CWE-798) that are enforced at startup even when administrators attempt to override them via environment variables, meaning operator-configured credentials do not replace the built-in ones.
  • Trigger conditions: No authentication, no special privileges, and no user interaction are required; network reachability to the Langflow HTTP/HTTPS interface is sufficient to attempt exploitation.
  • Attack vector: Remotely exploitable over the network (AV:N), with low attack complexity (AC:L) and no privilege or interaction dependencies (PR:N/UI:N).
  • Impact: Successful exploitation grants unauthorized superuser-level control of the Langflow instance, resulting in full compromise of confidentiality, integrity, and availability (C:H/I:H/A:H) — including the ability to read, modify, or destroy AI workflow data, pipeline configurations, and connected credentials.

Affected software

  • IBM Langflow OSS versions 1.0.0 through 1.10.1

Severity

  • CVSS v3.1 Base Score: 9.8 (CRITICAL)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Patch: Upgrade to IBM Langflow OSS version 1.10.2 or later, available via PyPI. IBM strongly recommends immediate upgrade.
  • Workarounds: IBM has confirmed that no workarounds are available for this vulnerability. Until patching is complete, organizations should restrict network access to Langflow instances and ensure they are not directly exposed to the public internet.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge