Seven more names hit the book. On 2 September 2026 CISA added seven vulnerabilities to the Known Exploited Vulnerabilities catalog on evidence of active exploitation. The agency’s own alert is the primary: CVE-2026-9586 Sangoma Switchvox; CVE-2026-48710 Kludex Starlette; CVE-2026-49869 Kestra OSS; CVE-2026-59822 BerriAI LiteLLM; CVE-2026-82329 JFrog Artifactory; CVE-2026-83548 and CVE-2026-83549 SonicWall SMA1000. Sunday 6 September. Frame it the way I always frame a KEV day: the catalogue named them, patches exist, agencies have dates. Not a lab manual.

Binding Operational Directive 26-04 is the clock for Federal Civilian Executive Branch agencies. CISA’s alert ties the new entries to BOD 26-04’s risk-based remediation rules for KEV-listed flaws on publicly exposed assets that grant total control after exploitation, and it reminds agencies to check whether someone was already in before the patch landed. Secondary wires I’m using — including The Hacker News’ 2 September filing — put remediation for most of the set around 5 September 2026, with Starlette and LiteLLM stretching to about 16 September. Those are federal clocks. Everyone else should still treat KEV as a prioritisation signal, which is exactly what CISA says in the same alert.

I’m going to name each entry the way the catalogue does, then stop. Sangoma Switchvox: SQL injection vulnerability, CVE-2026-9586. Starlette: HTTP request/response smuggling vulnerability, CVE-2026-48710. Kestra OSS: OS command injection vulnerability, CVE-2026-49869. LiteLLM: improper authentication vulnerability, CVE-2026-59822. JFrog Artifactory: improper authentication vulnerability, CVE-2026-82329. SonicWall SMA1000: server-side request forgery, CVE-2026-83548, and OS command injection, CVE-2026-83549. That is the public book. Vendors have published fixes and advisories for these products. Your job, if you run any of them on the open internet, is inventory, patch, and forensics — not fishing a newspaper for a reproduction path.

Seven more on the KEV
The Standard illustration

Positive fact, and I mean it: a public catalogue with CVE IDs, evidence-of-exploitation as the bar, and clear mitigation guidance is how a whole sector gets the same prioritisation list on the same morning. KEV is not a hall of fame for attackers. It’s a shared queue for defenders and for federal mandates. CISA even links a nomination form for exploited flaws that aren’t listed yet, with the bar stated up front — CVE ID, evidence of exploitation, clear mitigation guidance. That’s institutional machinery working in public. Celebrate the machinery. Don’t ask me to weaponise the footnotes.

What I’ll refuse, every time. I will not walk an exploit. I will not paste a PoC. I will not describe a payload or hand you enough detail to aim one. I will not turn SonicWall SMA1000, Switchvox, Artifactory, Kestra, Starlette, or LiteLLM into homework. The Hacker News and specialist write-ups that discuss observed exploitation in the wild are useful for urgency. They are not a licence for me to become a second-hand exploit kit. If your Tuesday is triage, use vendor advisories and your own change window. If your Tuesday is curiosity, go build a patch monitor instead.

Why this set feels like 2026 in one glance. You’ve got an edge VPN appliance family, a phone system, an artifact repository, an orchestration platform, a Python web toolkit that sits under a lot of FastAPI estates, and an AI gateway that proxies model calls. That’s not one “old server in a closet” story. That’s control planes, developer infrastructure, and the AI plumbing people stood up quickly. KEV doesn’t care about your roadmap slide. It cares that someone is already using the hole. The catalogue’s job is to say so in a sentence everyone can route into a ticket.

Deadlines again, because clocks are the actionable part. About 5 September 2026 for the federal remediation push on the bulk of this drop under BOD 26-04, on the secondary reporting I’m citing. About 16 September 2026 for CVE-2026-48710 and CVE-2026-59822 — Starlette and LiteLLM — on that same reporting. If you’re not an FCEB agency, you still own a calendar. Pull the KEV JSON. Diff it against your SBOM and your edge inventory. Patch what you run. Rotate what might have been touched. Verify from logs whether the box was quiet before the fix. That’s the grown-up loop. CISA’s alert literally tells federal shops to check pre-patch compromise. Steal that habit even if the directive doesn’t bind you.

Metric for the notebook. Catalog date: 2 September 2026. Count added: seven. CVE list as above. Directive: BOD 26-04. Approximate federal due dates in secondary coverage: 5 September for five of the seven, 16 September for Starlette and LiteLLM. File date: 6 September 2026, which means some of those federal clocks have already rung. If you’re late, you’re late — patch anyway, then do the compromise check with both eyes open.

Vendor posture, kept high level. Sangoma, SonicWall, JFrog, Kestra, Starlette maintainers, and LiteLLM maintainers have public security notes and fixed versions associated with these CVE IDs in the wider reporting. I’m not going to turn version pins into a second article inside this one. Go to the advisory for the product you actually ship. Apply the fixed build. Don’t run a random “check script” you found under a forum post that wants your production URL.

One more operational beat for teams that live in ticket templates. Map each CVE to an owner before the standup ends. Sangoma and SonicWall usually sit with voice or edge network. Artifactory sits with DevOps. Kestra sits with whoever owns orchestration. Starlette often hides under FastAPI services that never appear on a hardware inventory. LiteLLM sits with whoever stood up the AI gateway last quarter. The catalogue gave you names. Your CMDB has to give you people. That’s how seven CVEs become seven closed changes instead of one anxious Slack thread.

So here’s the hacking file. Seven more on the KEV. CISA named them on 2 September. BOD 26-04 gave agencies dates. Patches exist. The public book got longer, which is annoying and also how shared defence works. I’m not walking exploit steps. I’m not pasting a PoC. I’m not dropping payloads. Catalog, calendar, fix, verify. That’s the whole craft for a KEV Sunday. Log the CVEs. Close the tickets. Leave the theatre to people who don’t have pagers.

Last line for the wire. CVE-2026-9586, 48710, 49869, 59822, 82329, 83548, 83549. Seven strings. One catalogue. Two approximate federal deadline clusters. Naming exploited bugs in public is a defence win only if the next act is a patch, not a tutorial. Keep your edge inventory honest.