Date range covered: CISA additions dated November 13 to November 19, 2026. In that window the US Cybersecurity and Infrastructure Security Agency (CISA) added seven vulnerabilities to its Known Exploited Vulnerabilities (KEV) catalog, which means it has evidence each one is being used in real attacks. The additions came on three days: two on November 13, one on November 17 and four on November 18. At the time of writing, the catalog (version 2026.11.18, rechecked on November 20) showed no entries dated November 14, 15, 16 or 19. Due dates, vendors and descriptions below come from the KEV catalog and CISA’s alerts; fixes come from the vendor advisory where we could open it, and we say so where we could not. Our previous roundup covered November 6 to 12 and added the two November 13 entries as an update.
Which flaws have the shortest deadlines?
Federal civilian agencies must act by the date CISA sets, and everyone else uses it as a priority signal. CISA lists known ransomware use as “Unknown” for all seven.
- Already past due (November 16): UnrealIRCd CVE-2026-114713 and Check Point Gaia CVE-2026-123039.
- November 21: Synology DSM CVE-2024-10441, REDCap CVE-2026-90817 and Apache Axis CVE-2026-90436.
- December 1: Perforce Puppet Enterprise CVE-2026-115731.
- December 2: LiteLLM CVE-2026-40217.
November 13: UnrealIRCd and Check Point
From CISA’s November 13 alert:
- CVE-2026-114713, UnrealIRCd (due November 16): an escaping bug in the IRCv3 “label” tag lets any user on a network with two or more linked servers inject server-to-server commands that run with server authority. The hot-patch covers UnrealIRCd 6.0.0 through 6.2.7. The vendor advisory on oss-security says to run
./unrealircd hot-patch bundle-20261107on every server or upgrade to 6.2.7.1. UnrealIRCd 5 is also affected and has been end of life since July 2023. See our full UnrealIRCd guide. - CVE-2026-123039, Check Point Gaia (due November 16): the DynamicCLI daemon runs as root on a world-writable local socket and does not check who connects, so someone with local access to the appliance can run commands as root. Check Point advisory sk1000362 rates it 7.8 and says it saw an active exploit “against a couple of dozen customers.” The fix is the Jumbo Hotfix Accumulator: R82.20 Take 14 or later, R82.10 Take 52, R82 Take 132 and R81.20 Take 174. R81.10 and R81 are end of support with no fix listed, and Spark firewalls and Smart-1 Cloud are not affected. The workaround stops the dynamic_server process, which disables the Dynamic CLI commands. Our Check Point story covers the attacks.
November 17: Puppet Enterprise
From CISA’s November 17 alert:
- CVE-2026-115731, Perforce Puppet Enterprise (due December 1): a deserialization flaw in report processing lets a client holding any certificate signed by the Puppet CA run code on the Puppet Server as its service user. If the CA signs requests automatically without strong checks, an unauthenticated attacker can get a valid certificate first. SecurityWeek and Security Affairs report Perforce fixed it on November 3 in Puppet Enterprise 2026.0.1, 2025.12.1 and 2023.8.13 and Puppet Core 9.1.3 and 8.22.2. SecurityWeek quotes Perforce warning that a successful attack “could expose the server’s certificate-signing key.” Turn off automatic certificate signing until you have upgraded. Perforce’s own CVE page, which CISA links to, did not load for us, so check it for the exact versions.
November 18: Synology, LiteLLM, REDCap and Apache Axis
From CISA’s November 18 alert:
- CVE-2024-10441, Synology DiskStation Manager (due November 21): an improper output encoding flaw in the system plugin daemon that lets a remote attacker run code. It is not new: Synology-SA-24:20 was published in November 2024 and rates it Critical at 9.8. The fixed DSM versions are 7.2.2-72806-1, 7.2.1-69057-6, 7.2-64570-4, 7.1.1-42962-7 and 6.2.4-25556-8, each “or above.” The advisory lists no mitigation. CISA’s description also mentions BeeStation OS, so check Synology’s BeeStation advisory too.
- CVE-2026-40217, BerriAI LiteLLM (due December 2): a sandbox escape in the custom-code guardrail endpoint
/guardrails/test_custom_codethat needs an admin credential in default setups and runs as root in the default Docker image. The GitHub advisory covers 1.81.8 up to 1.83.10 and says the fix is 1.83.11 in its text, although a summary field says 1.83.10. Use 1.83.11 or later, or block that path at your gateway. - CVE-2026-90817, Vanderbilt REDCap (due November 21): a code injection flaw that lets an unauthenticated attacker run code on the server by sending crafted requests from a public survey context. Exploitation needs a valid public survey hash. The vendor’s advisory is behind REDCap’s login-restricted community site, so we could not read it. Security firm Ostorlab lists 17.4.4 (Standard), 17.3.10 (LTS) and 16.0.49 (LTS) as fixed releases, and says that disabling public surveys is a temporary containment only. Confirm the versions with Vanderbilt before you rely on them.
- CVE-2026-90436, Apache Axis (due November 21): an unsafe reflection flaw in Axis 1.x that lets an unauthenticated attacker run code through a crafted SOAP fault when a suitable class is on the classpath. Axis 1.x is end of life and, per Rapid7, Apache does not plan a fixed release. The real-world impact depends on the product that embeds it. Atlassian’s advisory says Confluence Data Center 1.x through 9.x is affected when the Remote API (XML-RPC and SOAP) setting is on, and lists 9.2.28 as the fix. Rapid7 saw exploitation against Confluence on November 13 and says N-able N-central 2026.4 HF3 (2026.4.1.39), released November 16, disables the vulnerable Legacy API. Our Confluence guide has the details.
What should you do this week?
- Check what you run. Look for Confluence Data Center with Remote API on, N-central, Puppet Server, LiteLLM, REDCap, Synology NAS, Check Point gateways and IRC servers.
- Start with internet-facing systems. CISA’s binding directive for federal agencies, BOD 26-04, puts known-exploited flaws on publicly exposed assets first.
- Patch, then look back. The directive also expects teams to check whether an attacker got in before the patch. Review logs, new accounts and unexpected child processes on anything that was exposed and unpatched.
- If you cannot patch, use the vendor’s workaround: switch off the Confluence Remote API, stop automatic Puppet certificate signing, block the LiteLLM endpoint, disable REDCap public surveys.
What is still unknown?
CISA’s alerts do not say who is exploiting these flaws, how many systems are affected or what attackers do after getting in. We could not read Perforce’s and REDCap’s own advisories. Anything CISA adds after the catalog version we checked falls outside this roundup.
Sources
- CISA alert, November 13, 2026
- CISA alert, November 17, 2026
- CISA alert, November 18, 2026
- CISA Known Exploited Vulnerabilities Catalog (version 2026.11.18, for due dates)
- SecurityWeek: Critical Perforce Puppet RCE exploited in attacks
Image: server racks in a data center, by PiDatacenters, CC BY-SA 4.0, via Wikimedia Commons.
Like our coverage? Add stepphase.com as a preferred source on Google to see more of our stories in Top Stories.
