CISA Adds Seven Exploited Flaws to KEV Catalog, SonicWall SMA 1000 CVSS 10.0 Leads

CISA added seven actively exploited vulnerabilities to its Known Exploited Vulnerabilities (KEV) catalog on September 2, and the entry at the top of the list carries the highest severity score the scale allows: a CVSS 10.0 server-side request forgery (SSRF) in SonicWall SMA 1000 Appliances, tracked as CVE-2026-83548. Across the seven, defenders are not looking at theoretical risk. Reverse shells and cryptocurrency miners have already been observed landing on vulnerable systems through several of the flaws.

That combination is the reason this KEV update matters more than most. The KEV catalog is the operational patch-priority list, the one place a security team can point to and say a flaw is being used against real targets right now, not just scored as dangerous in the abstract. When a maximum-severity, pre-authentication bug on an internet-facing gateway lands on it alongside confirmed miner and reverse-shell activity, the practical reading is that opportunistic mass-scanning for these products is already underway. This piece pulls the full list, flags which entries you can verify today, and lays out the response work in the order an operator should run it.

The Seven Flaws on the List

CISA published the additions in a single alert on September 2, spanning enterprise remote access, a build-artifact platform, VoIP, a Python web framework, and two pieces of AI infrastructure. The Hacker News enumerated the entries with their scores and vendors:

• CVE-2026-83548 (CVSS 10.0): a server-side request forgery (SSRF) flaw in SonicWall SMA 1000 Appliances that lets a remote, unauthenticated attacker reach sensitive functionality and perform unauthorized operations.
• CVE-2026-83549 (CVSS 7.8): a post-authentication operating system command injection flaw in SonicWall SMA 1000 Appliances that lets an authenticated administrator run arbitrary OS commands, ending in remote code execution.
• CVE-2026-9586 (CVSS 9.3): an SQL injection flaw in Sangoma Switchvox that lets an unauthenticated attacker run arbitrary SQL against the backend PostgreSQL database from a single crafted request.
• CVE-2026-82329 (CVSS 9.8): an improper authentication flaw in JFrog Artifactory that, under default configuration, hands an unauthenticated attacker with network access administrative privileges.
• CVE-2026-48710 (CVSS 6.5): an HTTP request and response smuggling flaw in Kludex Starlette that can lead to authentication bypass when auth depends on the reconstructed URL path.
• CVE-2026-49869 (CVSS 10.0): an operating system command injection flaw in Kestra OSS that lets an unauthenticated attacker create and run arbitrary workflows without credentials.
• CVE-2026-59822 (CVSS 8.8): an improper authentication flaw in Berri LiteLLM's Model Context Protocol (MCP) endpoint that lets an unauthenticated attacker open an authenticated MCP session with an arbitrary bearer token.

All seven CVE identifiers, vendors, and CVSS scores above are confirmed against The Hacker News reporting, which links each entry back to the underlying vendor advisory or CISA's own catalog. Two of the seven, the SonicWall pair, are the ones we covered at disclosure.

SonicWall's CVSS 10.0 Is the One to Move on First

If you run a SonicWall SMA 1000 appliance at your network edge, CVE-2026-83548 is your first job. A 10.0 is the ceiling of the CVSS scale, reserved for flaws that need no credentials and no user interaction, and this one sits on a remote-access gateway that is exposed to the public internet by design. Paired with CVE-2026-83549, the post-authentication command-injection bug in the same product line, the two chain into unauthenticated remote code execution on an unpatched box.

We detailed that chain when SonicWall disclosed it, in our coverage of the SMA 1000 zero-day chain under active attack. The short version for this piece: SonicWall's Product Security Incident Response Team said it "investigated a case indicating the active exploitation" of both flaws, there are no workarounds, and the only fix is the hotfix. The vulnerabilities affect the SMA 1000 series only (the 6210, 7210, and 8200v models), and they do not touch the SMA 100 series or SSL-VPN on SonicWall firewalls. If you manage one of these gateways, the KEV listing does not change the remediation, it raises the urgency: CISA is now telling you, on the record, that the flaw is being used in the wild.

Why Miners and Reverse Shells Change the Calculus

The post-exploitation behavior reported across the rest of the list is what turns this from a patch-notice into a hunt. Per The Hacker News, threat actors have been observed weaponizing the Sangoma Switchvox SQL injection (CVE-2026-9586) and the JFrog Artifactory authentication flaw (CVE-2026-82329) to deploy reverse shells and mint admin tokens for follow-on enumeration of users, groups, and credential sets, based on reporting from Horizon3.ai and watchTowr.

The two AI-infrastructure entries are worse in a different way. The Kestra OSS command-injection flaw (CVE-2026-49869) was added to KEV on the strength of a Microsoft report describing a compromise in which an attacker established a reverse shell, performed Docker container discovery, deployed a cryptocurrency miner, and harvested data. Microsoft summarized the Kestra case as exposing "four impact paths: shell execution through the workflow engine, container-environment exposure through Docker socket access, host resource hijacking through miner deployment, and follow-on collection through workflow task execution." Separately, Microsoft reported that attackers hitting Berri LiteLLM gateways delivered an XMRig miner via an ELF binary after fingerprinting the host and killing competing mining processes.

My read: the shape of this list tells you what to expect operationally. When a CVSS 10.0 on an exposed appliance shares a KEV entry with confirmed miner and reverse-shell activity on other products, you are almost certainly looking at broad, opportunistic scanning rather than a single targeted campaign. Miners are the tell. They are what commodity actors drop when they get a shell and have no better plan, which means the exploitation is being monetized at scale, which means exposure time is the whole game. I am labeling that as assessment, not reported fact. What is reported fact is the exploitation itself, the miner and reverse-shell payloads, and the severity scores. The defender move that follows is not "watch for a specific actor," it is "assume the internet is already testing your edge and shrink your exposure window to hours."

The Federal Clock, and Why It Is Your Clock Too

CISA's alert frames the additions in its standard language, and it is worth quoting because it is the agency's own justification for the list: "These types of vulnerabilities are frequent attack vectors for malicious cyber actors and pose significant risks to the federal enterprise," CISA wrote in the September 2 alert.

The binding requirement flows from Binding Operational Directive (BOD) 26-04, "Prioritizing Security Updates Based on Risk," which obligates Federal Civilian Executive Branch agencies to remediate KEV-listed flaws on a deadline. For this batch the clock is split. Agencies are directed to patch five of the seven by September 5, 2026, and have until September 16, 2026, to address the two exceptions, the Kludex Starlette (CVE-2026-48710) and Berri LiteLLM (CVE-2026-59822) flaws, according to The Hacker News. (Note for readers tracking the directive history: the earlier KEV mandate ran under BOD 22-01; the requirement CISA cites for these additions is BOD 26-04.)

Those deadlines legally bind federal agencies, but the logic behind them is universal. A KEV listing is the strongest practical signal a private-sector team can get that a flaw needs urgent attention, because inclusion requires confirmed exploitation. We made the same point when CISA added the ConnectWise ScreenConnect and Windows Shell flaws to the catalog in April: the federal deadline is a floor, not a target. If you run any of these seven products and they are exposed, September 5 is a reasonable date to hold yourself to whether or not you answer to CISA.

Here is how to work the list. The checklist below sequences the response for a team that has just seen this KEV update land.

KEV response playbook, sequenced for an operator: pull the seven entries, cross-check the inventory, patch the SonicWall CVSS 10.0 first, hunt for reverse-shell and miner indicators, meet the federal deadlines, and treat any exposed unpatched asset as breached until proven clean.

Two of the seven products carry an extra wrinkle worth naming. Artifactory, Kestra, and LiteLLM tend to live in developer environments rather than under central IT, so the asset-inventory step is where most teams will find their real exposure. An LLM gateway or a CI/CD artifact server that someone stood up for a project, then forgot, is exactly the kind of internet-facing box these campaigns are built to find. If the inventory step turns up something you did not know you were running, that is not a footnote, it is the finding.

For the broader logic of how to rank a list like this, which flaw to patch first when several land at once, and how exposure windows drive breach impact, our guide to vulnerability management lays out the prioritization framework that KEV is designed to feed.

Updated September 3, 2026: this is a developing story. Vendor advisories and CISA guidance may change; confirm the exact fixed versions and any indicators of compromise against the primary sources below.

Primary Documents

• CISA alert: CISA Adds Seven Known Exploited Vulnerabilities to Catalog (September 2, 2026)
• CISA Known Exploited Vulnerabilities Catalog
• The Hacker News: CISA Adds Seven Exploited Flaws as Attackers Deploy Reverse Shells and Crypto Miners
• The Hacker News: Attackers Exploit Two SonicWall SMA 1000 Zero-Days