Summary
- CISA has added three vulnerabilities to its Known Exploited Vulnerabilities Catalog based on evidence of active exploitation.
- The affected products are IBM Langflow (code injection), N-able N-central (authentication bypass), and Apache Tomcat (missing encryption of sensitive data).
- Under Binding Operational Directive 26-04, federal civilian agencies must prioritise rapid remediation of these vulnerabilities on publicly exposed assets.
- BOD 26-04 also requires agencies to assess whether systems were compromised before a patch was applied.
- CISA encourages all organisations — not just federal agencies — to treat KEV Catalog entries as high-priority remediation targets.
Three Products, Three Attack Vectors
CISA has confirmed active exploitation of vulnerabilities across three distinct products, adding all three to its Known Exploited Vulnerabilities Catalog. The affected software spans AI development tooling, IT management infrastructure, and a widely deployed web application server — a reminder that no category of enterprise software is insulated from attacker interest.
IBM Langflow: Code Injection Risk
The first entry, CVE-2026-9198, is a code injection vulnerability in IBM Langflow. Code injection flaws allow an attacker to introduce and execute arbitrary code within the context of the vulnerable application. Langflow is used for building AI-driven workflows, meaning environments running it may sit at the intersection of AI development pipelines and broader network infrastructure — a position that can amplify the impact of a successful compromise.
N-able N-central: Authentication Bypass
CVE-2026-18556 affects N-able N-central and is classified as an authentication bypass using an alternate path or channel. N-central is a remote monitoring and management platform used by managed service providers to oversee client environments. An authentication bypass in this class of tooling is particularly consequential: successful exploitation can grant an attacker access not just to one environment, but potentially to the downstream customer networks managed through the platform. MSPs and their customers should treat this one with particular attention.
Apache Tomcat: Sensitive Data Exposed Without Encryption
The third vulnerability, CVE-2026-34486, involves missing encryption of sensitive data in Apache Tomcat. Tomcat remains one of the most widely deployed Java-based web application servers in enterprise environments globally. While the nature of this flaw is distinct from remote code execution, the exposure of sensitive data in transit or at rest can feed subsequent attack stages, including credential theft and lateral movement.
What BOD 26-04 Changes for Federal Agencies
CISA’s Binding Operational Directive 26-04 establishes structured vulnerability management requirements for Federal Civilian Executive Branch agencies. It reinforces the KEV Catalog as a prioritisation tool and requires agencies to act rapidly on vulnerabilities listed there — specifically those present on publicly exposed assets where exploitation can result in full control of the affected system. Critically, BOD 26-04 also sets expectations around compromise assessment: agencies must determine whether a system was breached before a patch was applied, not simply patch and move on. That post-exploitation verification step is a meaningful addition to federal hygiene requirements.
Applicability Beyond Government
BOD 26-04 is binding only on federal civilian agencies, but CISA explicitly encourages all organisations to adopt the same risk-based approach. Confirmation of active exploitation — the threshold for KEV Catalog inclusion — means these are not theoretical risks. Threat actors are using these vulnerabilities now, and organisations that delay remediation based on lower internal risk scores may be underweighting that signal.
Why it matters
For CISOs, KEV Catalog additions represent one of the clearest threat intelligence signals available: confirmed exploitation in the wild, with CVE identifiers and mitigation guidance attached. All three vulnerabilities span high-value software categories — AI tooling, managed services platforms, and ubiquitous web infrastructure. Organisations running N-able N-central face supply-chain-adjacent risk that could extend exposure to client environments. The BOD 26-04 requirement to assess pre-patch compromise is also worth adopting as standard practice regardless of regulatory obligation; patching a system that was already compromised without verifying its integrity leaves the underlying problem unresolved.
What to do now
- Identify all instances of IBM Langflow, N-able N-central, and Apache Tomcat in your environment, including those managed by third parties or MSPs.
- Prioritise patching for any of the three affected products running on publicly exposed assets, consistent with CISA’s guidance on high-risk vulnerabilities.
- After patching, conduct a compromise assessment to determine whether exploitation occurred prior to remediation — do not assume a clean state based on the patch alone.
- If your organisation uses an MSP that runs N-able N-central, request confirmation that CVE-2026-18556 has been remediated and ask for evidence of a post-patch integrity review.
- Incorporate the CISA KEV Catalog into your vulnerability management prioritisation process if not already in use, treating KEV entries as elevated-priority remediation targets.
- If your organisation is aware of an exploited vulnerability not yet listed in the KEV Catalog, submit it via CISA’s KEV Nomination Form.
