IBM Langflow OSS'dagi yettita zaiflikni, jumladan autentifikatsiyani chetlab o'tish va kod in'ektsiyasi kabi muhim kamchiliklarni e'lon qildi; hujumchilar ularni masofadan turib, hech qanday hisob ma'lumotlarisiz ishlatishi mumkin. Byulleten Langflow 1.0.0 dan 1.12.8 gacha bo'lgan versiyalarni qamrab oladi va administratorlarga 1.13.0 versiyasiga yangilashni tavsiya qiladi.
IBMning 28-oktabrda e'lon qilingan va 29-oktabrda yangilangan xavfsizlik byulleteniga ko'ra, ushbu zaifliklar ixtiyoriy kod bajarish, API hisob ma'lumotlarining fosh bo'lishi, autentifikatsiyani chetlab o'tish va bog'liq bog'liqliklar bilan bog'liq hujumlarga olib kelishi mumkin. Ikki zaiflik CVSS balli 9.8 ga ega bo'lib, bu past murakkablikdagi tarmoq orqali, hech qanday imtiyoz yoki foydalanuvchi o'zaro ta'sirisiz ishlatilishi mumkinligini anglatadi.
CVE-2026-93680 noto'g'ri autentifikatsiya bilan bog'liq bo'lib, masofaviy hujumchilarga xavfsizlik cheklovlarini chetlab o'tishga imkon beradi. IBMning xulosasida asosiy muammolar orasida avtomatik kirish xavfsizlik nazoratining to'liq tuzatilmagani ham qayd etilgan. CVE-2026-110186 esa kod generatsiyasini yetarlicha nazorat qilmaslik orqali ixtiyoriy kod bajarishga imkon beradi.
Byulleten shuningdek, Model Context Protocol (MCP) vositalarini ro'yxatga olish orqali erishish mumkin bo'lgan autentifikatsiyasiz masofaviy kod bajarishni ham tasvirlaydi. Biroq, uning alohida CVE tavsiflari har bir umumlashtirilgan hujum mexanizmini aniq identifikatorga bog'lamaydi. Ushbu xavflar zaif MCP serverlarining hujum yuzasini kengaytiradi, chunki tashqi integratsiyalar sezgir funksionallikni fosh qilishi mumkin.
CVE-2026-110193 past imtiyozli autentifikatsiyalangan hisobni talab qiladi. Hujumchi Agentic Assistant'ni bloklanmagan naqshlarni o'z ichiga olgan komponent kodini generatsiya qilish yoki yuborishga majbur qilishi mumkin, natijada serverda operatsion tizim buyruqlari bajariladi. CVE-2026-110192 esa autentifikatsiyalangan hujumchilarga yetarlicha himoyalanmagan hisob ma'lumotlari orqali sezgir ma'lumotlarni olishga imkon beradi.
Farq muhim: har bir muammo autentifikatsiyasiz emas va byulleten hujumchilarning ushbu zaifliklarni zanjir qilib ishlatishi shart emasligini ta'kidlamaydi. Langflow'ning ta'siri ayniqsa jiddiy, chunki Langflow serverlariga qarshi kriptomayning hujumlari allaqachon alohida, eski zaiflikdan foydalanib amalga oshirilgan.
CVE tafsilotlari
IBM quyidagi zaifliklarni, jumladan Hono framework bog'liqligidagi uchta muammoni ro'yxatga olgan. Ballar CVSS v3.1 asosiy ballaridir.
| CVE | Komponent | CVSS | Ta'sir |
|---|---|---|---|
| CVE-2026-93680 | Langflow | 9.8 | Autentifikatsiyasiz autentifikatsiyani chetlab o'tish |
| CVE-2026-110186 | Langflow | 9.8 | Autentifikatsiyasiz ixtiyoriy kod bajarish |
| CVE-2026-110193 | Langflow | 8.8 | Autentifikatsiyalangan server buyruqlarini bajarish |
| CVE-2026-110192 | Langflow | 6.5 | Autentifikatsiyalangan sezgir ma'lumot fosh bo'lishi |
| CVE-2026-84363 | Hono | 5.9 | So'rov talqinidagi nomuvofiqlik; kesh zaharlanishi |
| CVE-2026-84364 | Hono | 5.3 | Ichki obyektlar orqali xotira tugashi |
| CVE-2026-84365 | Hono | 6.5 | Qurilish vaqtidagi yo'l o'tishi |
Hono'ning kesh muammosi URL so'rovlarida haqiqiy hash belgilarini saqlaydigan infratuzilmani talab qiladi. Uning xotira tugashi kamchiligi nuqta-notatsiya (dot-notation) tanasi tahlili yoqilgan nuqtalarga ta'sir qiladi, bu esa standart emas. Yo'l o'tishi zaifligi ishonchsiz marshrut parametrlari bilan statik sayt generatsiyasiga ta'sir qiladi, oddiy so'rov vaqtidagi marshrutlashga emas. Uchala muammo ham Hono 4.13.5 da tuzatilgan.
Administratorlar ta'sirlangan o'rnatmalarni pip install –upgrade "langflow==1.13.0" buyrug'i yoki langflowai/langflow:1.13.0 Docker tasviri orqali Langflow 1.13.0 ga yangilashlari kerak. Bu boshqa Langflow zaiflik byulleteni bilan bog'liq tuzatish relizini almashtiradi.
Yangilashdan oldin ma'lumotlar bazasi, maxfiy kalit va yuklangan fayllarni zaxiralang. Avtomatik kirish (automatic-login) o'rnatmalarida mavjud hisoblarni parol bilan kirish uchun tayyorlang. Docker operatorlari konteynerlarni qayta yaratishdan oldin doimiy saqlashni tekshirishlari kerak, chunki noto'g'ri sozlangan o'rnatish ma'lumotlar bazasi va hisob ma'lumotlarini yo'qotishi mumkin. IBM alohida oraliq yechim (workaround) taqdim etmaydi.
SOC'ga hodisalarni tez to'xtatish uchun ogohlantirish kontekstini bering. 16K SOC'dan tahdid razvedkasini integratsiya qiling.
IBM has disclosed seven vulnerabilities in Langflow OSS, including critical flaws such as authentication bypass and code injection that attackers can exploit remotely without credentials. The bulletin addresses Langflow versions 1.0.0 through 1.12.8 and advises administrators to upgrade to version 1.13.0.
According to IBM’s security bulletin, published October 28 and updated October 29, the vulnerabilities could enable arbitrary code execution, API credential exposure, authentication bypass, and attacks involving bundled dependencies. Two vulnerabilities carry CVSS scores of 9.8, indicating low-complexity network exploitation without privileges or user interaction.
CVE-2026-93680 involves improper authentication, allowing remote attackers to bypass security restrictions. IBM’s summary identifies incomplete remediation of an automatic-login security control among the underlying issues. Separately, CVE-2026-110186 permits arbitrary code execution through insufficient control over code generation.
The bulletin also describes unauthenticated remote code execution reachable through Model Context Protocol tool enumeration. However, its individual CVE descriptions do not explicitly map every summarized attack mechanism to a specific identifier. These risks expand the attack surface of vulnerable MCP servers, where external integrations can expose sensitive functionality.
CVE-2026-110193 requires a low-privileged authenticated account. An attacker could cause the Agentic Assistant to generate or submit component code containing unblocked patterns, resulting in operating system command execution on the server. CVE-2026-110192 separately enables authenticated attackers to obtain sensitive information through insufficiently protected credentials.
The distinction matters: not every issue is unauthenticated, and the bulletin does not establish that attackers must chain these vulnerabilities. Langflow’s exposure is particularly consequential because cryptomining attacks against Langflow servers have already exploited a separate, older vulnerability.
CVE Details
IBM lists the following vulnerabilities, including three issues in the Hono framework dependency. Scores are CVSS v3.1 base scores.
| CVE | Component | CVSS | Impact |
|---|---|---|---|
| CVE-2026-93680 | Langflow | 9.8 | Unauthenticated authentication bypass |
| CVE-2026-110186 | Langflow | 9.8 | Unauthenticated arbitrary code execution |
| CVE-2026-110193 | Langflow | 8.8 | Authenticated server command execution |
| CVE-2026-110192 | Langflow | 6.5 | Authenticated sensitive-information disclosure |
| CVE-2026-84363 | Hono | 5.9 | Request interpretation inconsistency; cache poisoning |
| CVE-2026-84364 | Hono | 5.3 | Memory exhaustion through nested objects |
| CVE-2026-84365 | Hono | 6.5 | Build-time path traversal |
Hono’s cache issue requires infrastructure that preserves literal hash characters in request URLs. Its memory-exhaustion flaw affects endpoints with dot-notation body parsing enabled, which is not the default. The traversal vulnerability affects static-site generation using untrusted route parameters, not ordinary request-time routing. All three are fixed in Hono 4.13.5.
Administrators should upgrade affected installations to Langflow 1.13.0 using pip install –upgrade “langflow==1.13.0” or the Docker image langflowai/langflow:1.13.0. This replace the remediation release associated with another Langflow vulnerability bulletin.
Before upgrading, back up the database, secret key, and uploaded files. Automatic-login deployments must prepare existing accounts for password sign-in. Docker operators should verify persistent storage before recreating containers, since a misconfigured deployment can lose its database and credentials. IBM provides no separate interim workaround.
Give your SOC the alert context to stops incidents quickly.Integrate Threat Intel from 16K SOCs.