The Cybersecurity and Infrastructure Security Agency added two unauthenticated remote code execution vulnerabilities — a new Langflow RCE identified as CVE-2026-0770 and the WordPress wp2shell plugin flaw CVE-2026-63030 — to its Known Exploited Vulnerabilities catalog on July 22, 2026, setting separate federal remediation deadlines: July 24 for Langflow and August 4 for WordPress. Both CVEs carry a CVSS score of 9.8. CISA’s catalog addition confirmed active exploitation already underway for both platforms, with mass scanning and attacks beginning before the federal mandate.
CVE-2026-0770 and CVE-2026-63030: Two 9.8-Severity RCEs Under Active Exploitation
CVE-2026-0770 is an unauthenticated remote code execution vulnerability in Langflow — the open-source AI workflow automation platform used to build and deploy AI agent pipelines. This is a distinct and separately identified Langflow RCE from all prior CVEs covering the platform: it is not CVE-2025-3248, not CVE-2026-5027, and not any Langflow vulnerability addressed in previous CISA KEV additions. CISA’s July 24 deadline — 72 hours after the KEV addition — signals that CISA assessed active, urgent exploitation of this CVE at the time of catalog addition.
CVE-2026-63030 is an interpretation conflict vulnerability in the WordPress wp2shell plugin that enables unauthenticated remote code execution. The flaw allows an attacker to deploy web shells on a vulnerable WordPress installation without any authentication. Mass scanning began immediately when the flaw was first publicly documented, and active exploitation was confirmed before CISA’s formal catalog addition.
Both CVEs represent a consistent pattern in the current threat environment: public disclosure of a high-severity unauthenticated RCE triggers immediate mass exploitation by adversaries scanning for unpatched instances at internet scale.
CVE-2026-63030 and the WordPress wp2shell Plugin’s Web Shell Deployment Path
The WordPress wp2shell plugin is the affected software for CVE-2026-63030. An attacker who successfully exploits CVE-2026-63030 gains persistent code execution on the web server hosting the WordPress installation, enabling file system access, credential harvesting from configuration files, lateral movement to connected databases, and persistence through additional shell placements.
The wp2shell designation reflects the attack’s core capability: transforming an unauthenticated HTTP request into a deployed web shell on a WordPress server without any prior access or credential. Once a web shell is in place, the WordPress server effectively becomes an attacker-controlled node accessible through a web-facing interface.
WordPress installations running the wp2shell plugin and not yet running a patched version remain exposed to unauthenticated web shell deployment. Given the confirmed active exploitation, remediation should be treated as urgent regardless of whether the affected organization is a federal agency subject to the KEV mandate.
Langflow’s Third Exploited CVE in 2026 and the Platform’s Sustained Vulnerability History
CVE-2026-0770 is the third separate Langflow CVE to be confirmed exploited in 2026. Two prior Langflow RCEs — CVE-2025-3248 (exploited by the JADEPUFFER ransomware operator for ENCFORGE delivery) and CVE-2026-5027 (a path traversal RCE documented in a prior CISA advisory) — established Langflow as a platform under sustained adversarial attention.
The recurrence of newly discovered, independently exploitable RCE vulnerabilities across three separate CVE identifiers in a single platform within one year indicates that Langflow’s code execution attack surface has attracted significant adversarial research and exploitation investment. Organizations running Langflow as part of AI agent infrastructure should assess whether each new Langflow CVE they patch represents the full scope of their exposure, given the demonstrated pattern of successive new exploitation vulnerabilities following each prior remediation.
Langflow’s role as AI agent infrastructure amplifies the impact of RCE on its deployments: Langflow instances typically have access to AI model APIs, data pipelines, and backend services that feed AI agent functionality. Code execution on a Langflow server provides access to API keys, credentials, and data flows that extend well beyond the Langflow process itself.
Remediating CVE-2026-0770 and CVE-2026-63030 Before the Federal Deadlines
CISA set different remediation windows for each CVE under Binding Operational Directive 26-04: Langflow CVE-2026-0770 carries a July 24 deadline — one of CISA’s most aggressive timelines — while WordPress CVE-2026-63030 carries an August 4 deadline. Both deadlines apply formally to FCEB agencies, but any organization running either platform should treat the respective date as its emergency remediation target given confirmed mass exploitation.
Langflow deployments should be updated to a patched version addressing CVE-2026-0770 and should be assessed for any signs of prior exploitation — unexpected outbound connections, unusual process spawning from the Langflow service, or unauthorized changes to pipeline configurations or API key storage. WordPress installations running the wp2shell plugin should update to a patched version immediately and should be reviewed for deployed web shells in locations outside the expected WordPress directory structure or with unusual file permissions.
Organizations that have applied previous Langflow patches for CVE-2025-3248 or CVE-2026-5027 should not assume those patches address CVE-2026-0770 — it is a distinct, separately patched vulnerability requiring its own update.
