CVE-2026-17628Patch

LOWCVSS 5.4 · MEDIUM

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Patch affected systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD description

IBM Langflow OSS 1.0.0 through 1.10.2 could allow a remote authenticated attacker to change the password of an account due to improper authentication.

0.5/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-287

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

NONE

Threat summary

  • Patch or workaround signal is available
  • 1 mentions across 1 observed day

What's happening

  • Patch or workaround mentioned in 1 signal
  • Technical details provided in 1 signal
  • 1 total mentions across 1 day

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-09-16: 1Patch / Workaround · 2026-09-16: 1Technical Details · 2026-09-16: 109-16
Signal classification1 categories
Patch
1100.0%
Referenced assets2 URLs
Full discourse1 post
  • hackerlogs@hackerlogs
    Patch

    @IBM's @langflow_ai scanner said validated. The CVE is 9.6 anyway. CVE-2026-12944 (CVSS 9.6, authenticated): Langflow OSS 1.0.0 through 1.10.0. An authenticated user could submit a flow component the scanner marked validated while network standard-library code still ran as UID 0. IBM's fix for that row is 1.10.1. Take 1.10.3 for CVE-2026-17628 (password-reset miss). No confirmed exploitation on 12944 yet. A green validated badge is a blocklist, not a sandbox. This is not CVE-2026-0768 (the unauthenticated Langflow RCE @cloudsa watched harvesting cloud keys in August). Same host, different class. Rotate keys after you upgrade. Primary (IBM bulletin): https://www.ibm.com/support/pages/security-bulletin-incomplete-security-scanner-blocklist-enables-network-based-code-execution-0 Write-up: https://hackerlogs.com/blog/langflow-cve-2026-12944/

    Post summary

    The tweet discloses CVE‑2026‑12944, an authenticated CVSS 9.6 code execution vulnerability in Langflow OSS 1.0.0‑1.10.0 caused by a scanner‑validated blocklist, and notes that IBM has released fixes (1.10.1 for this CVE and 1.10.3 for a related issue) with no confirmed exploitation yet.

    0001064
    15 followersView on X

Explore more