August 5, 2026 is shaping up to be a demanding day for security teams. CISA has expanded its Known Exploited Vulnerabilities catalog with three new entries, all confirmed to be under active exploitation in the wild, while the National Vulnerability Database has simultaneously published two additional critical-severity disclosures. The common thread running through today's briefing is trust abuse: attackers are targeting the platforms organizations rely on to manage infrastructure, run AI workflows, serve web applications, and publish content. When the tools meant to keep systems running become the attack surface, defenders must respond with urgency.

The most alarming of today's additions is CVE-2026-9198, a code injection vulnerability in IBM Langflow. Langflow is an AI workflow orchestration platform increasingly adopted by enterprises building and deploying large language model pipelines. Code injection flaws in this class of tool are particularly dangerous because they sit at the intersection of trusted internal tooling and powerful compute resources. An attacker who can inject and execute code through Langflow effectively gains a foothold inside the AI infrastructure layer, which often carries elevated permissions and broad network access. CISA's confirmation of active exploitation means this is not theoretical. Organizations running IBM Langflow must treat patching as an emergency action and, in the interim, restrict access to the Langflow interface to trusted internal networks only.

CVE-2026-18556 affects N-able N-central, a widely deployed remote monitoring and management platform used by managed service providers and enterprise IT teams. The vulnerability is an authentication bypass via an alternate path or channel, meaning an attacker can circumvent the login process entirely and gain access to the management console without valid credentials. RMM platforms are high-value targets because they provide privileged, broad access to managed endpoints across entire client environments. A compromise here is not a single-system incident; it is a potential mass deployment event. MSPs in particular should treat this as a critical business continuity issue and apply vendor patches immediately, enforce network-level access controls on the N-central interface, and audit recent access logs for anomalous authentication patterns.

CVE-2026-34486 rounds out the CISA KEV additions with a missing encryption of sensitive data vulnerability in Apache Tomcat. While the description may sound less dramatic than code injection or authentication bypass, the active exploitation status changes the calculus entirely. Sensitive data transmitted or stored without proper encryption can expose credentials, session tokens, or application secrets that enable follow-on attacks. Apache Tomcat underpins a vast number of Java web applications in enterprise environments. Defenders should verify that all Tomcat deployments are running patched versions, confirm that TLS is enforced on all connectors, and review application configurations for any legacy settings that may disable or weaken encryption.

Beyond the KEV catalog, two additional vulnerabilities warrant immediate attention. CVE-2026-15435 is a path traversal flaw in IBM App Connect Enterprise affecting versions 12.0.1.0 through 12.0.12.27 and 13.0.1.0 through 13.0.7.2, carrying a CVSS score of 9.8. The vulnerability allows unauthenticated remote attackers to write arbitrary files to the server by crafting URL requests with directory traversal sequences. Arbitrary file write at this severity level can lead to web shell deployment, configuration tampering, or full system compromise. Any organization running IBM App Connect Enterprise in the affected version ranges should prioritize patching above almost everything else on today's list given the CVSS score and the remote, unauthenticated nature of the attack.

Finally, CVE-2026-67351 affects Serendipity, a PHP-based blogging and CMS platform, in versions prior to 2.6.1. Authenticated users with the Editor role can escalate their privileges to Administrator by exploiting a username collision flaw between the password validation and session loading processes. While this requires an existing authenticated account, insider threat scenarios and compromised low-privilege accounts make privilege escalation bugs genuinely dangerous. Organizations using Serendipity should upgrade to version 2.6.1 or later immediately and audit current user accounts for any unexpected role assignments.

Defensive priorities for today:

- Patch IBM Langflow immediately and restrict interface access to trusted networks pending deployment
- Apply N-able N-central patches as an emergency action; audit RMM access logs for unauthorized sessions and enforce IP allowlisting on the management console
- Update Apache Tomcat to the vendor-recommended patched release and enforce TLS across all application connectors
- Patch IBM App Connect Enterprise to a non-vulnerable version as the highest CVSS priority; block external access to the integration server management interfaces where possible
- Upgrade Serendipity to 2.6.1 or later and review all CMS user accounts for unauthorized privilege changes
- Cross-reference your asset inventory against all six CVEs and escalate any unpatched internet-facing instances to incident response priority
- Ensure EDR and SIEM alerting is tuned to detect unusual process execution from web application service accounts, which may indicate post-exploitation activity on Tomcat or App Connect hosts

The convergence of AI platform vulnerabilities, RMM tool weaknesses, and foundational web server flaws in a single day's briefing is a reminder that attackers are opportunistic and systematic. Defenders who move quickly on patching and access restriction today will significantly reduce their exposure window.

This briefing is informational only and does not substitute for official vendor security advisories; always consult vendor guidance for authoritative patch and mitigation instructions.