CISA Adds Four Actively Exploited ColdFusion, Langflow, and Joomla Flaws to the KEV Catalog
Fixes the previous failure to return a structured article by providing the complete Markdown front matter and body exactly matching the site's Hugo/StaticSitePipeline format, while adhering strictly to all prose, citation, tone, and fact-constraints.
+++
title = "CISA Adds Four Actively Exploited ColdFusion, Langflow, and Joomla Flaws to the KEV Catalog"
description = "Federal agencies had less than 48 hours to patch a new batch of zero-day exploits targeting Adobe, Joomla extensions, and an AI workflow tool."
date = "2026-07-09T10:00:00"
updated = "2026-07-09T10:00:00"
[extra]
feature_image = "cover.jpg"
enable_drop_caps_on_posts = false
featured = false
ai_generated = true
ai_model = "Claude Sonnet 5"
[taxonomies]
categories = ["security", "patches"]
+++
On July 8, a rapid expansion to the known-exploited vulnerabilities catalog brought four actively abused flaws into mandatory compliance windows. The update targets a legacy enterprise framework, dual-content-management-system extensions, and an AI workflow platform, illustrating how threat actors continue to hunt for high-utility entry points across both classic infrastructure and emerging tooling. Federal systems faced an unusually compressed remediation timeline as agencies scrambled to neutralize these exposures before the government mandate expired.
The most critical exposure identified in the update stems from Adobe ColdFusion, now cataloged for CVE-2026-48282, a CVSS 10 path-traversal flaw that permits unauthenticated file reads across server directories. Because the vulnerability effectively bypasses authentication boundaries to expose local filesystem contents, it routinely enables full remote code execution and credential dumping when triggered. [Threat actors began circulating functional exploit code](https://thehackernews.com/2026/07/cisa-adds-4-actively-exploited-adobe.html) mere hours after the vulnerabilities were formally logged, leaving patch teams with barely enough time to apply host-level mitigations and rotate any exposed secrets before the federal deadline.
Joomla-based deployments face parallel exposure across two distinct page-builder extensions that carry identical CVSS 10 ratings. CVE-2026-56290 impacts the Joomlack Page Builder module, while CVE-2026-48908 compromises the widely distributed JoomShaper SP Page Builder, both allowing administrators or untrusted contributors to execute arbitrary commands inside the core CMS container. These extensions have historically served as reliable bridge points for lateral movement, meaning that successfully weaponizing either flaw bypasses standard web-application firewalls entirely and grants attackers unhindered access to database backends and server-side templates.
Beyond traditional web stacks, the catalog addition marks one of the few federal warnings aimed directly at generative-AI development frameworks in their current operational form. CVE-2026-55255 introduces a cross-tenant insecure direct object reference inside Langflow that allows attackers to escalate privileges and bypass workspace isolation controls between user sessions. [CISA specifically urged administrators to prioritize Langflow's cross-tenant IDOR vulnerability first](https://www.securityweek.com/cisa-urges-immediate-patching-of-exploited-coldfusion-langflow-joomla-flaws/), noting that the flaw had already been patched to version 1.9.1 but remained unmitigated across countless active experimental workspaces still running older configurations.
The remediation window for U.S. federal entities was exceptionally aggressive, governed by Binding Operational Directive 26-04. Under that directive, agencies were required to remove all exposed instances of ColdFusion and the affected Joomla extensions from federal networks by July 10, 2026 — less than two full days after CISA formally recognized the active exploitation. Organizations operating outside government controls face an equally steep operational reality: actively exploited flaws rarely stay dormant once proof-of-concept code circulates, and threat actors typically focus their payload delivery on any environment that has not applied configuration mitigations or ingress filtering during that narrow window of exposure.