Skip to main content
Back
IntrusionAWS
9 min read

NATS-as-C2: Langflow flaw to an AWS key replay and Bedrock attempts

Victim
The unnamed owner of an internet-exposed Langflow instance
When
Session date not stated – May 5, 2026Disclosed May 14, 2026
Entry
Unauthenticated code execution through the public flow build endpoint of an internet-exposed Langflow instance (CVE-2026-33017), whose process environment held an AWS access key.

The Sysdig Threat Research Team captured a session, identified on May 5, 2026, in which an operator ran code on an internet-exposed Langflow instance through its unauthenticated public flow build endpoint (CVE-2026-33017) and dumped the AWS access key held in the process environment. Nine minutes later the AWS identity check accepted the key from the operator's address at a hosting provider, and the operator attempted Bedrock model invocation, which Sysdig reads as an attempt at LLMjacking, and swept the account's services; Sysdig states no outcome for any call after the identity check. The operator then deployed a worker on the host that takes tasks from its NATS server, and the sources do not say whether the host was a Sysdig-run sensor, whose AWS account the key reached, or where the host ran.

What happened

External Parties
Operator's NATS server
Operator's staging server
Sysdig Threat Research
Internet
AWS APIstolen access key
Langflow
AI Workflow Host
Key's AWS Account
Langflow Instance
AWS Key in Environment
AWS Service APIs
Amazon Bedrock

Replaying the Langflow NATS-as-C2 May 2026 intrusion / session undated; Sysdig identified it on May 5, 2026

  1. 1

    Langflow host, then the AWS key

    Session day (undated), 09:09–09:12 UTC

    An unauthenticated flaw in the public flow build endpoint runs the operator's code on the Langflow host, and the AWS key in its process environment is dumped.

  2. 2

    Key replayed against AWS

    Session day (undated), 09:21–13:39 UTC

    The AWS identity check accepts the stolen key from the operator's address, and the key sweeps the account's services with no outcome stated.

  3. 3

    Bedrock tried with the key

    Session day (undated), 09:21–13:39 UTC

    The key attempts Bedrock model invocation and lists inference profiles and model invocation jobs; the sources state no outcome, no model and no cost.

  4. 4

    Worker on the Langflow host

    Session day (undated), 14:03 UTC

    The operator returns to the host and deploys a worker that takes tasks from its NATS server; an installer that makes it a system service is not confirmed to have run.

Impact

An AWS key dumped from an exposed Langflow instance was accepted by the AWS identity check from the operator's address, then used to attempt Bedrock model invocation and to sweep the account's services, and a worker was deployed on the host. No outcome of the AWS calls after the identity check, no cost and no data loss is stated.

Outcome

Where the provider's controls fit

On AWS, a security group, or a declarative policy that sets VPC Block Public Access to ingress-only, bounds who can reach your Langflow port from the internet, and a security group's outbound rules bound where the host can connect. Both act only on a host in an AWS VPC, and the sources do not say where this host ran or state outright that the worker on it connected to the operator's server. A service control policy that lets only an approved administrator role create access keys would have kept a workload to a role credential that expires; the sources do not say whether the dumped key was a long-term key. A service control policy that refuses calls from outside your networks, or IAM user calls without MFA, would have bounded the replayed key, but not its identity check, which needs no permission. A service control policy that keeps Bedrock to your networks, or to approved models, would have bounded the invocation attempts, whose outcome the sources do not state. None of these service control policies binds the management account. No cloud control reaches the flaw in Langflow, which 1.9.0 fixes, the read of the process environment, or the worker started on the host.

Could this have been prevented?

In hindsight, no control would have stopped it. 10 controls would have limited how far it went. 3 steps have no cloud-provider control. The counts below are control assessments, not attack stages: several can address the same step. The same replay with the controls in place before the incident shows where each phase would have been refused or bounded.

0
Prevented
10
Contained
3
Not covered

How it could have been prevented

The same replay with the controls in place. Green marks where a step is refused, blue where it is bounded, and red where no control reaches it. Open a row to read the control, why it acts, and its caveat.

External Parties
Operator's NATS server
Operator's staging server
Sysdig Threat Research
Internet
AWS APIstolen access key
Langflow
AI Workflow Host
Key's AWS Account
Langflow Instance
AWS Key in Environment
AWS Service APIs
Amazon Bedrock

Replaying the Langflow NATS-as-C2 May 2026 intrusion / session undated; Sysdig identified it on May 5, 2026

1 · Langflow host, then the AWS key

3 Contained2 Not covered6 on other clouds

2 · Key replayed against AWS

4 Contained6 on other clouds

3 · Bedrock tried with the key

2 Contained5 on other clouds

4 · Worker on the Langflow host

1 Contained1 Not covered3 on other clouds

Key facts

  • On March 16, 2026, Langflow published an advisory for an unauthenticated code execution flaw in its public flow build endpoint (CVE-2026-33017), affecting 1.8.2 and earlier and fixed in 1.9.0; Sysdig states that the CVE was added to CISA's Known Exploited Vulnerabilities catalog on March 25, 2026
  • On a session day that Sysdig did not date beyond identifying the activity on May 5, 2026, the operator ran code on the Langflow target without authentication at 09:12 UTC, three minutes after its first probe, and the payload dumped the process environment with an AWS access key ID and secret access key
  • At 09:21 UTC, nine minutes after the dump, the AWS STS identity check accepted the key from the operator's address at a hosting provider; the kind of identity the key belonged to and its policies were not stated
  • Between 09:21 and 13:39 UTC the operator called 11 AWS services with the key, among them Bedrock model invocation attempts and listings of inference profiles and model invocation jobs; Sysdig stated no outcome for any call after the identity check, and no cost
  • At 14:03 UTC the operator returned to the host to deploy a worker that takes tasks from its NATS server; a compiled worker failed, a Python worker remained the working path, and an installer that sets it up as a system service was not confirmed to have run
  • Sysdig did not say whether the Langflow host was a sensor it ran or a third party's instance, whose AWS account the key reached, or where the host ran

Sources

Every fact in this breakdown comes from the public reporting below. The replay is a model of that reporting, not a reconstruction of the environment it describes.

  1. 1.
    NATS-as-C2: Inside a new technique attackers are using to harvest cloud credentials and AI API keysSysdig · May 14, 2026 · ResearchEntry vector, environment dump, AWS key replay, Bedrock attempts, service sweep, NATS worker, timeline
  2. 2.
    Unauthenticated Remote Code Execution in Langflow via Public Flow Build EndpointLangflow · Mar 16, 2026 · AdvisoryVulnerability, affected versions, fix

The estate in the replay is illustrative and drawn at the level of attack stages; the victim's real environment is not public. Verdicts describe what a control does when it is in place before the incident. They are not an assessment of the victim's security program.

More cloud attack breakdowns

All breakdowns