CISA Adds Seven Exploited Flaws to KEV Catalog

CISA Adds Seven Actively Exploited Flaws to KEV Catalog

CRITICAL
September 3, 2026
September 5, 2026
m read
VulnerabilityPatch ManagementThreat Intelligence

Related Entities(initial)

Threat Actors

Qilin

Organizations

CISAJFrogMicrosoftSonicWall

Products & Tech

Berri LiteLLMJFrog ArtifactoryKestraKestra OSSKludex StarletteSangoma SwitchvoxSonicWall SMA 1000

Other

Cryptocurrency miner

CVE Identifiers

CVE-2026-48710
MEDIUM
CVSS:6.5
CVE-2026-49869
CRITICAL
CVSS:10
CVE-2026-59822
HIGH
CVSS:8.8
CVE-2026-82329
CRITICAL
CVSS:9.8
CVE-2026-83548
CRITICAL
CVSS:10
CVE-2026-83549
HIGH
CVSS:7.8
CVE-2026-9586
CRITICAL
CVSS:9.3

Full Report(when first published)

Executive Summary

On September 2, 2026, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added seven actively exploited vulnerabilities to its Known Exploited Vulnerabilities (KEV) catalog. This action mandates that Federal Civilian Executive Branch (FCEB) agencies remediate these flaws under accelerated timelines set by the new Binding Operational Directive (BOD) 26-04. The vulnerabilities affect a range of products, including SonicWall SMA 1000 appliances, Kestra OSS, and JFrog Artifactory. Exploitation in the wild has been confirmed, with activities ranging from cryptocurrency mining and data harvesting to ransomware deployment by groups such as Qilin.


Vulnerability Details

The seven vulnerabilities added to the KEV catalog represent significant risks to organizations due to confirmed in-the-wild exploitation. The flaws and their impacts are as follows:

  • CVE-2026-83548: A critical server-side request forgery (SSRF) vulnerability in SonicWall SMA 1000 appliances with a CVSS score of 10.0. It allows an unauthenticated attacker to access sensitive functionality and is being chained with CVE-2026-83549.
  • CVE-2026-83549: A post-authentication OS command injection vulnerability in SonicWall SMA 1000 appliances (CVSS 7.8). When chained, it allows for full remote code execution.
  • CVE-2026-49869: A critical OS command injection vulnerability in Kestra OSS (CVSS 10.0). Microsoft reported its exploitation to establish reverse shells, deploy cryptocurrency miners, and exfiltrate data.
  • CVE-2026-82329: A critical improper authentication vulnerability in JFrog Artifactory (CVSS 9.8). Attackers are exploiting this to gain administrative privileges by minting admin tokens.
  • CVE-2026-9586: An SQL injection vulnerability in Sangoma Switchvox (CVSS 9.3), enabling attackers to exfiltrate database information.
  • CVE-2026-48710: An HTTP request smuggling flaw in Kludex Starlette (CVSS 6.5). Its exploitation has been linked to the Qilin ransomware group.
  • CVE-2026-59822: An improper authentication bug in Berri LiteLLM (CVSS 8.8). This is also being exploited by Qilin to target AI infrastructure, steal API keys, and monetize compromised hosts.

Affected Systems

The following products and versions are confirmed to be affected by the vulnerabilities added to the KEV catalog:

  • SonicWall SMA 1000 series appliances
  • Kestra OSS
  • JFrog Artifactory
  • Sangoma Switchvox
  • Kludex Starlette
  • Berri LiteLLM

Exploitation Status

All seven vulnerabilities have confirmed evidence of active exploitation in the wild. Attackers are using the Kestra flaw for resource hijacking and data theft. The JFrog vulnerability is being used to gain administrative control. The SonicWall flaws are being chained for unauthenticated remote code execution. The Starlette and LiteLLM vulnerabilities are being leveraged by the Qilin ransomware group in attacks on AI infrastructure.

Impact Assessment

The addition of these vulnerabilities to the KEV catalog underscores their significant risk. For FCEB agencies, the deadlines under BOD 26-04 are non-negotiable, with most requiring remediation by September 5, 2026. For private organizations, these vulnerabilities pose a severe threat of network compromise, data exfiltration, ransomware deployment, and resource hijacking. The exploitation of flaws in remote access solutions like SonicWall SMA 1000 and AI-related tools like LiteLLM highlights threat actors' focus on high-value perimeter devices and emerging technology stacks.


Cyber Observables — Hunting Hints

Security teams can hunt for potential exploitation activity related to these vulnerabilities. The following patterns could indicate related activity:

Type
url_pattern
Value
/cgi-bin/sslvpn-login
Description
Potential target for SSRF attempts against SonicWall SMA 1000.
Type
process_name
Value
xmrig
Description
A common cryptocurrency miner often deployed after initial compromise.
Type
command_line_pattern
Value
`curl *
Description
sh`
Type
log_source
Value
Artifactory access logs
Description
Monitor for successful authentication events from untrusted IP addresses or attempts to mint new tokens.
Type
network_traffic_pattern
Value
Outbound traffic to known cryptomining pools
Description
Indicates potential resource hijacking on a compromised host.

Detection & Response

Defenders should prioritize detection strategies focused on both initial access and post-exploitation activity.

  1. Network Monitoring: Implement rules to detect anomalous requests to affected appliances like SonicWall SMA 1000. Monitor for SSRF signatures, such as URLs containing internal IP addresses or localhost. Use Network Traffic Analysis (D3-NTA) to baseline traffic from these devices and alert on unusual outbound connections.
  2. Log Analysis: Ingest and analyze web server, application, and authentication logs from all affected products. For the JFrog flaw, search for anomalous token creation events. For Kestra, look for child processes spawned by the Kestra service, especially shell processes (sh, bash) or tools like curl and wget.
  3. Endpoint Detection (EDR): Deploy EDR agents on servers hosting these applications. Monitor for suspicious process chains, command-line arguments, and file modifications. A rule to detect a Java process spawning a shell is a high-fidelity indicator for the Kestra flaw.

Mitigation

The most effective mitigation is to apply the security updates provided by the respective vendors immediately. However, where patching is not immediately feasible, consider the following compensating controls:

  1. Patch Management: Prioritize applying patches for all seven vulnerabilities, starting with internet-facing systems. This is the most critical action. This aligns with D3FEND Software Update (D3-SU).
  2. Restrict Access: Limit network access to the management interfaces of affected devices. For SonicWall SMA and JFrog Artifactory, ensure management portals are not exposed to the public internet and are only accessible from a trusted internal network or via a secure VPN.
  3. Web Application Firewall (WAF): Deploy a WAF with rulesets designed to block SSRF, SQL injection, and command injection attacks. This can provide a virtual patch while testing and deploying official vendor updates.
  4. Network Segmentation: Segment networks to prevent lateral movement from a compromised perimeter device. This can limit the blast radius if an attacker successfully exploits a flaw like the one in the SonicWall appliance.

Timeline of Events

1
June 10, 2026
CISA issues Binding Operational Directive (BOD) 26-04, introducing new risk-based patching timelines.
2
September 2, 2026
CISA adds seven new vulnerabilities to the Known Exploited Vulnerabilities (KEV) catalog.
3
September 3, 2026
This article was published
4
September 5, 2026
Patching deadline for most of the newly added KEVs for FCEB agencies.

Article Updates

September 4, 2026

Severity increased

New analysis highlights that three of the seven CISA KEV vulnerabilities specifically target AI/ML infrastructure, leading to risks like supply chain attacks and model theft.

Further analysis of the CISA KEV update reveals a significant focus on AI/ML infrastructure, with CVE-2026-82329 (JFrog Artifactory), CVE-2026-59822 (LiteLLM), and CVE-2026-48710 (Starlette) directly impacting AI development tools. This update underscores new risks such as supply chain attacks via compromised Artifactory, data poisoning, model theft, and resource hijacking for cryptocurrency mining, particularly by the Qilin ransomware group. The targeting of the entire MLOps pipeline, from data orchestration to model deployment, signifies a growing threat to AI-driven workflows.

September 5, 2026

New details on CISA's KEV additions include specific patch deadlines, deeper analysis of AI infrastructure exploitation, and new mitigation strategies.

The update provides specific patch deadlines for each of the seven CISA KEV vulnerabilities, with some due by September 5 and others by September 16, 2026. It also offers a more detailed technical analysis of how AI infrastructure flaws (like LiteLLM) are exploited to steal API keys for services such as OpenAI and Azure, and to deploy crypto miners. New detection and mitigation strategies, including monitoring cloud billing for API usage spikes and implementing credential management for AI platforms, are also highlighted. The article also notes CISA's action on September 4, 2026, in addition to the previously reported September 2.

Timeline of Events

1
June 10, 2026

CISA issues Binding Operational Directive (BOD) 26-04, introducing new risk-based patching timelines.

2
September 2, 2026

CISA adds seven new vulnerabilities to the Known Exploited Vulnerabilities (KEV) catalog.

3
September 5, 2026

Patching deadline for most of the newly added KEVs for FCEB agencies.

Sources & References(when first published)

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Editorial Standards & Analyst Review

CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.

Tags

BOD 26-04CISACommand InjectionKEVQilinRansomwareSSRF

📢 Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

🛡️ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

🔗 STIX Visualizer

Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.

⚡ Sigma Generator

Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.