Agent incident · Sep 8, 2026

JADEPUFFER. The access path.

An LLM-driven operation harvested credentials and encrypted 1,342 config items. From Langflow exploitation to database extortion: the role of harvested credentials.

langflow-rceCVE-2025-3248, unpatched, exposedEntry
llm-agentautonomous recon + planning
harvested-credsAI keys, cloud creds, wallets
lateral-movementreuse creds to reach databasesReached
SEP 8, 2026

The record

Entry point. langflow-rce, CVE-2025-3248, unpatched, exposed.

The identity in the middle. Cloud credentials, AI API keys and wallets harvested from the compromised Langflow host.

What was reached. databases reached with harvested credentials, 1,342 config items encrypted.

AT A GLANCE

An LLM-driven operation harvested credentials and encrypted 1,342 config items.

PATH

The path, step by step.

Taken from the published reporting. Nothing here is reconstructed.

StepRole in the pathWhat the reporting records
langflow-rceEntryCVE-2025-3248, unpatched, exposed
llm-agentStepautonomous recon + planning
harvested-credsStepAI keys, cloud creds, wallets
lateral-movementReachedreuse creds to reach databases
BREAKPOINT

Where a breakpoint would have been

The long-lived credentials readable on that host. The CVE bought the first step only; everything after it ran on secrets that were sitting there, so removing them stalls the agent at step one.

A breakpoint is the single change that closes a path with the least disruption. Read how that is chosen in the breakpoint page. The full narrative is in the teardown.

ELMOZ ASSESSMENT

4 steps from entry to data.

PRIMARY SOURCES

Where this comes from.

Every field on this page is taken from the published reporting below. The breakpoint assessment is Elmoz reading that path, not a statement about what the affected organisation did.

Sysdig · The Register

FAQ

Questions, answered.

The two questions this record answers.

What was the entry point in the JADEPUFFER incident?

The published path starts at langflow-rce, CVE-2025-3248, unpatched, exposed.

What did it reach?

The published path ends at databases reached with harvested credentials, 1,342 config items encrypted.

See what your agents can reach. Before someone else does.

Book a demo and we walk through the access paths in an environment like yours.