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

Back
New CVE Detected

CVE-2026-7874 – Credential Disclosure via Weak Encryption at Rest – IBM Langflow OSS 1.0.0–1.10.0

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-7874 is a critical credential disclosure vulnerability in IBM Langflow OSS versions 1.0.0 through 1.10.0, caused by the use of a weak and reversible key derivation mechanism for encryption at rest. With a CVSS v3.1 base score of 9.1 (Critical), this flaw allows unauthenticated remote attackers to decrypt and access all credentials stored by the platform. IBM has released version 1.10.1 to address this issue and recommends immediate upgrade.

Technical details

  • Root cause: Langflow OSS derives Fernet encryption keys using Python’s non-cryptographic Mersenne Twister PRNG seeded with the application’s SECRET_KEY, rather than a cryptographically secure key derivation function (CWE-338). When SECRET_KEY is fewer than 32 characters, the resulting encryption key is fully deterministic and reproducible; even with longer keys, the raw SECRET_KEY value is used directly as the encryption key, bypassing appropriate key stretching.
  • Trigger conditions: No authentication or user interaction is required to exploit this flaw (PR:N, UI:N), and attack complexity is low (AC:L).
  • Attack vector: Network-based (AV:N); the vulnerability is remotely exploitable over the internet with no requirement for local access.
  • Impact: Full disclosure of all credentials stored at rest within the platform — including LLM provider API keys, database passwords, and third-party integration secrets — representing critical confidentiality (C:H) and integrity (I:H) impact.

Affected software

  • IBM Langflow OSS versions 1.0.0 through 1.10.0

Severity

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

Mitigation and recommended actions

  • Immediate: Upgrade IBM Langflow OSS to version 1.10.1, available on PyPI, which resolves this vulnerability.
  • No documented workarounds exist; patching is the only recommended remediation.
  • As a precautionary measure, rotate all credentials previously stored within Langflow (API keys, database passwords, OAuth tokens) immediately, as values encrypted by the vulnerable mechanism may have already been exposed.

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