Case · DiggingBeagle record

An attacker harvested decoy Flowise secrets and submitted offensive agent prompts

Assessment profile

Assessment method
Setting
controlled live
Exploitation
observed live
Evidence
Grade B
AI role
AGAINST AI
Basis and provenance

CLM-SEKOIA-FLOWISE-HONEYPOT-1 reports: The honeypot simulated Flowise 2.2.8 without executing real model inference or system code. Its attacker prompts therefore establish attempted misuse, not a successful LLM-led intrusion. Source SRC-2026-CP17-SEKOIA-FLOWISE is located at 'Context and perimeter: Sekoia Honeypot overview'. The distinctive mechanism begins: Sekoia emulated the Flowise 2.2.8 REST surface in a deception service, with decoy credentials and synthetic chatflows but no live model execution or operating-system shell. Classification: setting=controlled_live, exploit_status=observed_live, evidence_grade=B on the bounded original investigator/vendor or paper evidence, without independent dynamic replication. remediation_status=unknown; scoped control or limit: Protect chatflow and credential APIs through authentication and authorization, constrain outbound workflow destinations and treat the textual request to the model as untrusted. The honeypot was designed to answer probes, so its apparent responses cannot be read as production exploitation results. The null impact band avoids an ungrounded cross-Case severity rating; observed damage, targeted population and controlled test outcomes cannot be exchanged as the same quantity. Where a patch is described, its availability is separate from independently tested effectiveness.

Assessed Oct 23, 2026 using diggingbeagle.assessment/1.

At a glance

Timeline

  1. Oct 19, 2026
    disclosure

    Public disclosure

Claims & evidence

CLM-SEKOIA-FLOWISE-HONEYPOT-1The honeypot simulated Flowise 2.2.8 without executing real model inference or system code. Its attacker prompts therefore establish attempted misuse, not a successful LLM-led intrusion.supported

Basis: reported finding

Link to claim
CLM-SEKOIA-FLOWISE-HONEYPOT-2The observed attack principally abused exposed legitimate functionality; the historical authentication-bypass CVE was explanatory context, not a vulnerability exploited in version 2.2.8.supported

Basis: reported finding

Link to claim

Controls and mitigations

  • Protect chatflow and credential APIs through authentication and authorization, constrain outbound workflow destinations and treat the textual request to the model as untrusted. The honeypot was designed to answer probes, so its apparent responses cannot be read as production exploitation results.

Unknowns and contradictions

  • Production victim impact and actual agent compliance are unestablished.

Sources and citation

Material revision history

  1. Oct 23, 2026 · Canonical change recorded · new in release · revision 183