Yes. CISA added CVE-2026-0770 to its Known Exploited Vulnerabilities catalogue on 21 July 2026, which it does only when there is reliable evidence of active exploitation. CISA has not linked it to known ransomware campaigns. Langflow contains an inclusion of functionality from untrusted control sphere vulnerability that allows remote attackers to execute arbitrary code on affected installations.
What “exploited in the wild” means for this CVE
CISA’s KEV listing is the practical signal that matters here. For CVE-2026-0770, it indicates the flaw is not just theoretical, so the right assumption is that exposure needs immediate attention, not routine queueing. If you run Langflow, confirm whether any deployed instance is internet-facing, reachable through a shared network segment, or used by teams that connect it to sensitive tools, data, or credentials.
Because the issue is an inclusion of functionality from an untrusted control sphere, the impact is not limited to a crash or local misbehavior. The concern is that attacker-controlled input can steer execution into arbitrary code on the affected system. That changes triage from “patch eventually” to “treat as a potential remote-code-execution exposure with compromise-assessment value.”
For a background model of how active exploitation changes prioritisation, use the Zero-Day and Exploited Vulnerabilities Guide to align urgency with KEV status, exposure, and post-patch verification.
How to confirm exposure and contain the blast radius
Start by locating every Langflow deployment, including test, staging, ephemeral, and self-hosted instances that may have been forgotten. Then verify whether the service is reachable by untrusted users or connected to data sources, model endpoints, internal APIs, or automation paths that would make arbitrary code execution materially more dangerous.
If the service is exposed, isolate it before the full remediation cycle completes. That can mean restricting network access, disabling public reachability, revoking temporary access paths, or taking the instance offline if the business process can tolerate it. For an RCE-class flaw, containment is not a substitute for remediation, but it can narrow the attacker’s window while you verify the environment.
Use the Vulnerability Management Guide to structure exposure confirmation, prioritisation, exceptions, and verification once the fix is applied.
For the authoritative vulnerability record and any vendor-linked fix guidance, check the CVE Program and the CISA Known Exploited Vulnerabilities Catalog rather than relying on summaries alone.
What to do if patching must wait
If you cannot remediate immediately, treat the system as high-risk until you have reduced the exposure path. The most effective temporary controls are the ones that stop untrusted parties from reaching the vulnerable surface, reduce the privileges of the service account running the application, and limit the downstream resources that a compromised process could touch.
When patching is delayed, document the exception with an expiry date and a compensating-control owner. In practice, that means you should not leave an exploited vulnerability sitting in an indefinite risk acceptance because “the app is internal” or “the code path is hard to test.” The issue has already crossed into confirmed exploitation territory, so delay needs to be time-bound and visible.
Use FIRST EPSS as a secondary prioritisation input, but do not let probability scoring override the KEV signal when active exploitation is already established.
For teams that want a broader operating model for fast-moving exposure response, the Vulnerability Management Guide is the right companion for exception handling, SLAs, and post-remediation validation.
Risk and Threat Considerations
Active exploitation changes the problem from “a vulnerable application exists” to “an attacker may already have a working path to code execution.” With a flaw like inclusion of functionality from an untrusted control sphere, the most important risk is uncontrolled execution on a host that may already trust internal data, tokens, or connected services.
Failure mechanism: Untrusted input or externally influenced control flow is accepted as if it were safe, allowing the attacker to trigger code paths that were never meant to be attacker-controlled.
Impact: The result can be remote code execution, follow-on credential theft, lateral movement, or abuse of the application as a pivot point into adjacent systems.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
CIS Controls v8, NIST CSF 2.0 and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| CIS Controls v8 | CIS-7 — Continuous Vulnerability Management | CVE exploitation demands rapid identification and remediation of affected assets. |
| Recommendation — Prioritise the vulnerable Langflow assets for expedited remediation and verification. | ||
| NIST CSF 2.0 | ID.RA-01 — Asset Vulnerabilities Are Identified and Recorded | Active exploitation response depends on identifying exposed vulnerable instances. |
| PR.PS-03 — Configuration Management | Containment and hardening reduce exposure while remediation is pending. | |
| RS.MA-01 — Mitigation Is Executed | KEV-listed exploitation calls for rapid mitigation of the vulnerable condition. | |
| Recommendation — Inventory Langflow deployments and record exposure status for immediate action. Restrict access and harden the Langflow deployment until remediation is complete. Execute the fix or compensating mitigation as soon as possible. | ||
| NIST SP 800-53 Rev 5 | RA-5 — Vulnerability Monitoring and Scanning | Confirmed exploitation requires scanning and tracking vulnerable installations. |
| Recommendation — Scan for affected Langflow instances and validate remediation status. | ||
Practitioner Guidance
What to verify: Confirm whether any Langflow instance is exposed to untrusted users or sits near sensitive secrets, API keys, internal APIs, or automation that would increase blast radius if code execution is achieved. If the app can touch production data or inherited credentials, treat compromise assessment as part of the same workstream as patching.
Decision rule: If the instance is reachable outside a tightly controlled admin path, prioritise containment and rotation of exposed credentials or tokens before you spend time debating whether exploitation has occurred locally. If it is isolated and not connected to sensitive systems, remediation is still urgent, but the immediate blast radius is lower.
Practitioner takeaway: For a KEV-listed flaw with confirmed exploitation, the right question is not whether the vulnerability is interesting, it is whether the affected instance can still be reached, abused, or used as a foothold right now.
Related resources from NHI Mgmt Group
- CVE-2026-0770 (Langflow Inclusion of Functionality from Untrusted Control Sphere)
- Is CVE-2025-32463 (Sudo Inclusion of Functionality from Untrusted Control Sphere) being exploited in the wild?
- Is CVE-2026-20131 (Cisco Secure Firewall Management Center (FMC) Software and Cisco Security Cloud Control (SCC) Firewall Management Deserialization of Untrusted Data) being exploited in the wild?
- How do you patch or mitigate CVE-2025-32463 (Sudo Inclusion of Functionality from Untrusted Control Sphere)?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 19, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org