📄 Description (English)
Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.0, /api/v1/public-chatbotConfig/:id ep exposes sensitive data including API keys, HTTP authorization headers and internal configuration without any authentication. An attacker with knowledge just of a chatflow UUID can retrieve credentials stored in password type fields and HTTP headers, leading to credential theft and more. This vulnerability is fixed in 3.1.0.
🤖 AI Executive Summary
Flowise versions prior to 3.1.0 expose sensitive data including API keys, HTTP authorization headers, and internal configuration through an unauthenticated API endpoint. An attacker with only a chatflow UUID can retrieve stored credentials, leading to credential theft and potential lateral movement. This vulnerability poses significant risk to organizations deploying Flowise for AI/LLM applications, particularly those handling sensitive business logic or integrations.
📄 Description (Arabic)
🤖 AI Intelligence Analysis Analyzed: May 2, 2026 06:55
🇸🇦 Saudi Arabia Impact Assessment
Saudi organizations in financial services (banking sector under SAMA oversight), government agencies (NCA jurisdiction), healthcare providers, and energy sector (ARAMCO and subsidiaries) face significant risk if deploying Flowise for customer-facing AI chatbots or internal LLM workflows. The exposure of API keys and authorization headers could compromise integrations with critical backend systems, payment gateways, and sensitive databases. Government entities and critical infrastructure operators are particularly vulnerable due to the potential for credential theft leading to unauthorized access to classified or sensitive systems.
🏢 Affected Saudi Sectors
Banking and Financial Services
Government and Public Administration
Healthcare and Medical Services
Energy and Utilities
Telecommunications
E-commerce and Retail
Insurance
Education
🎯 MITRE ATT&CK Techniques
⚖️ Saudi Risk Score (AI)
8.2
/ 10.0
🔧 Remediation Steps (English)
IMMEDIATE ACTIONS:
1. Identify all Flowise instances in your environment and document their versions
2. Audit access logs for the /api/v1/public-chatbotConfig/:id endpoint to detect potential exploitation
3. Rotate all API keys, credentials, and HTTP authorization headers that may have been exposed
4. Implement network-level access controls to restrict access to Flowise instances
PATCHING:
1. Upgrade to Flowise 3.1.0 or later immediately when available
2. If upgrade is not immediately possible, disable or restrict access to the /api/v1/public-chatbotConfig/:id endpoint
COMPENSATING CONTROLS:
1. Implement Web Application Firewall (WAF) rules to block requests to /api/v1/public-chatbotConfig/:id endpoint
2. Deploy API gateway authentication layer requiring valid credentials for all API access
3. Implement IP whitelisting to restrict access to Flowise instances to known trusted networks
4. Enable comprehensive API logging and monitoring for all Flowise endpoints
5. Implement secrets management solution to store credentials outside of Flowise configuration
DETECTION:
1. Monitor for HTTP GET/POST requests to /api/v1/public-chatbotConfig/ with UUID parameters
2. Alert on successful responses containing 'apiKey', 'authorization', or 'password' fields from this endpoint
3. Track unusual access patterns to this endpoint from external IP addresses
4. Implement SIEM rules to detect credential extraction attempts
🔧 خطوات المعالجة (العربية)
الإجراءات الفورية:
1. تحديد جميع مثيلات Flowise في بيئتك وتوثيق إصداراتها
2. تدقيق سجلات الوصول لنقطة النهاية /api/v1/public-chatbotConfig/:id للكشف عن الاستغلال المحتمل
3. تدوير جميع مفاتيح API وبيانات الاعتماد ورؤوس التفويض HTTP التي قد تكون قد تعرضت
4. تنفيذ عناصر تحكم الوصول على مستوى الشبكة لتقييد الوصول إلى مثيلات Flowise
التصحيح:
1. الترقية إلى Flowise 3.1.0 أو إصدار أحدث فوراً عند توفره
2. إذا لم يكن الترقية ممكنة فوراً، قم بتعطيل أو تقييد الوصول إلى نقطة النهاية
عناصر التحكم البديلة:
1. تنفيذ قواعد جدار حماية تطبيقات الويب لحظر الطلبات إلى نقطة النهاية
2. نشر طبقة مصادقة بوابة API تتطلب بيانات اعتماد صحيحة
3. تنفيذ القائمة البيضاء للعناوين IP لتقييد الوصول إلى الشبكات الموثوقة
4. تفعيل السجلات الشاملة ومراقبة جميع نقاط نهاية Flowise
5. تنفيذ حل إدارة الأسرار لتخزين بيانات الاعتماد خارج التكوين
الكشف:
1. مراقبة طلبات HTTP إلى نقطة النهاية مع معاملات UUID
2. التنبيه على الاستجابات الناجحة التي تحتوي على حقول حساسة
3. تتبع أنماط الوصول غير العادية من عناوين IP خارجية
4. تنفيذ قواعد SIEM للكشف عن محاولات استخراج بيانات الاعتماد
📋 Regulatory Compliance Mapping
🟢 NCA ECC 2024
ECC 2024 - 5.1.1: Access Control and Authentication
ECC 2024 - 5.2.1: Cryptographic Controls
ECC 2024 - 6.1.1: Incident Detection and Response
ECC 2024 - 7.1.1: Data Protection and Privacy
🔵 SAMA CSF
SAMA CSF - Governance: Information Security Governance
SAMA CSF - Protect: Access Control and Authentication
SAMA CSF - Protect: Data Protection
SAMA CSF - Detect: Security Monitoring and Logging
🟡 ISO 27001:2022
ISO 27001:2022 - A.5.2: User Access Management
ISO 27001:2022 - A.5.3: Access Rights
ISO 27001:2022 - A.8.2: Cryptography
ISO 27001:2022 - A.8.3: Cryptographic Key Management
ISO 27001:2022 - A.12.4: Logging
🟣 PCI DSS v4.0.1
PCI DSS 4.1: Render PAN unreadable
PCI DSS 6.2: Security patches and updates
PCI DSS 7.1: Limit access to system components
PCI DSS 10.2: Implement automated audit trails
📦 Affected Products / CPE 1 entries
flowiseai:flowise