Daily threat watch, 20 November 2026: 5 exploited CVEs added this week, 3 to act on now
The bottom line
Three fixes are due first, by 21 November 2026: Synology DiskStation and BeeStation, REDCap, and Apache Axis version 1 — all let an attacker run code on a server or device without logging in. Find whether you run any, then update; Apache Axis has no fix, so take it off the network. Puppet and LiteLLM follow in early December.
CISA added 5 vulnerabilities to its exploited list from 14 November 2026 to 20 November 2026. 3 have a deadline within three days or already past.
Separately, 1522 new CVE records were published in the last 30 hours, 202 of them scored 8 or higher. They are in the day's CVE highlight, not on this list, because nothing says yet that anyone is using them.
Free analysis report · 7 pagesDaily threat watch, 20 November 2026: 5 exploited CVEs added this week, 3 to act on nowThe same note as a document you can keep or forward: what the sources say, who is affected, and what to do first.Download the analysis report →What changed since the last watch
- Left the seven-day window (33): CVE-2026-123039, CVE-2026-114713, CVE-2026-116606, CVE-2026-111560, CVE-2026-124194, CVE-2026-20320, CVE-2026-125350, CVE-2026-111793, CVE-2026-123158, CVE-2026-116779, CVE-2026-123218, CVE-2026-102895, CVE-2026-19868, CVE-2026-119977, CVE-2024-27834, CVE-2026-111357, CVE-2026-118527, CVE-2026-97229, CVE-2026-76418, CVE-2026-46300, CVE-2026-41709, CVE-2026-111497, CVE-2026-48356, CVE-2026-109618, CVE-2026-109619, CVE-2026-104935, CVE-2026-59309, CVE-2026-59310, CVE-2026-47876, CVE-2026-41703, CVE-2024-27833, CVE-2024-27851, CVE-2024-27808.
Nothing new was added since yesterday's watch, so there is nothing fresh to compare. Several items from earlier in the week have rolled off, and no deadlines passed in between. The five below are what is left to act on.
At a glance
| Entry | Act | CISA date | Fixed in | EPSS |
|---|---|---|---|---|
| Vanderbilt University Research Electronic Data Capture (REDCap) (CVE-2026-90817) | Today | Due tomorrow | REDCap 16.0.49 LTS, 17.3.10 LTS or 17.4.4 Standard Release, as applicable (CVE record; no fix date given) | 0.04 |
| Synology DiskStation Manager (DSM) (CVE-2024-10441) | Today | Due tomorrow | DSM 7.2.2-72806-1, 7.2.1-69057-6, 7.2-64570-4, 7.1.1-42962-7; BSM 1.1-65374 (vendor advisory, first published 5 November 2024) | 0.01 |
| Apache Axis (CVE-2026-90436) | Today | Due tomorrow | None recorded; version 1 is unsupported. The record advises stopping use or moving to a supported product. | 0.01 |
| Perforce Puppet Enterprise (CVE-2026-115731) | Next patch cycle | Due in 11 days | Puppet Enterprise 2023.8.13, 2025.12.1 or 2026.0.1 (these bundle puppet-agent 8.22.2 or 9.1.3), then restart puppet server. The record says so; no vendor page was read. | 0.01 |
| BerriAI LiteLLM (CVE-2026-40217) | Next patch cycle | Due in 12 days | No fixed version is stated in the sources. | 0.17 |
How the week connects
All five are remote code execution on server software. Four need no login: REDCap (with a known survey link), Apache Axis, Synology and, where signing is automatic, Puppet; only LiteLLM needs an existing account. REDCap and Puppet share the same code-generation weakness, and both Axis and Puppet run attacker-chosen code by turning untrusted input into objects. Otherwise the products are unrelated.
Do this today, in this order
- Vanderbilt University Research Electronic Data Capture (REDCap), CVE-2026-90817, due tomorrow. A research data tool used by universities and health teams. Someone with no login, who knows a public survey's web link, can run code on the server. Anyone running REDCap must look.
- Synology DiskStation Manager (DSM), CVE-2024-10441, due tomorrow. Network storage boxes from Synology, including BeeStation. A remote attacker can run code on the device with no login. Anyone with one on their network must look.
- Apache Axis, CVE-2026-90436, due tomorrow. An older web-services component inside some Java applications. A crafted message can make it run an attacker's code with no login. Version 1 is unsupported, so find what uses it.
The first hour:
- Find any Synology DiskStation or BeeStation, read each version, and update to the fixed DSM or BSM build. CISA's date is 21 November 2026.
- Find any REDCap server and upgrade it to 16.0.49, 17.3.10 or 17.4.4. Also due 21 November 2026.
- Find where Apache Axis version 1 runs; there is no fix, so take it off the network. Also 21 November 2026.
- Then handle Puppet Enterprise (1 December 2026) and LiteLLM (2 December 2026).
- Vanderbilt University Research Electronic Data Capture (REDCap), CVE-2026-90817 →The full analysis, who is affected, and the analysis report.
- Synology DiskStation Manager (DSM), CVE-2024-10441 →The full analysis, who is affected, and the analysis report.
- Apache Axis, CVE-2026-90436 →The full analysis, who is affected, and the analysis report.
In the next patch cycle
- Perforce Puppet Enterprise, CVE-2026-115731, due in 11 days. Server software that configures fleets of machines. A host with a signed certificate — or an outsider where signing is automatic — can run code on the Puppet server. Users must look.
- BerriAI LiteLLM, CVE-2026-40217, due in 12 days. A proxy placed in front of AI services. Someone already logged in to it can run code on the host through a test endpoint. Whoever operates it must look.
- Perforce Puppet Enterprise, CVE-2026-115731 →The full analysis, who is affected, and the analysis report.
- BerriAI LiteLLM, CVE-2026-40217 →The full analysis, who is affected, and the analysis report.
Who can skip most of this
If you run none of these — REDCap, Apache Axis, Synology storage, Puppet Enterprise or LiteLLM — this week does not need your time. That does not mean you are safe from other flaws.
Send this to your IT provider
Copy it, change the names and dates, and send it. It is a draft for you to check, not a template tested with any provider.
Hello. CISA has flagged five products we want to be sure about. Three have a deadline of 21 November 2026: Synology DiskStation and BeeStation (CVE-2024-10441), REDCap (CVE-2026-90817) and Apache Axis version 1 (CVE-2026-90436). Two more fall due in early December: Puppet Enterprise (CVE-2026-115731) on 1 December 2026 and LiteLLM (CVE-2026-40217) on 2 December 2026. Please confirm in writing whether we run any of these, the exact version of each, and whether it is on the fixed release — or, for Apache Axis, taken off the network, as no fix exists. Could we have that by the end of this week? Thank you.
Check it yourself in two minutes
Everything above comes from public sources. This command prints CISA's additions in the same period with their due dates:
curl -s https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json \
| jq -r '.vulnerabilities[] | select(.dateAdded >= "2026-11-14" and .dateAdded <= "2026-11-20")
| [.cveID,.dateAdded,.dueDate,.vendorProject,.product] | @tsv' | sort -k2Run on 20 November 2026 it printed 5 rows, the ones above. A later run may show more.
Check your own project
If you build software, you can compare what a project declares with these CVEs from a terminal. The tool reads requirements files, package.json, Maven, Gradle, Cargo, CMake and Dockerfile files, runs nothing, and only the CVE ids leave your machine. Naming the CVEs needs no key.
lattice-scan project . --cve CVE-2026-90817,CVE-2024-10441,CVE-2026-90436,CVE-2026-115731,CVE-2026-40217Each row says in-range, outside-range, undetermined or lead, with the file and line. That is evidence about what a manifest declares, not about what runs, and a person decides. The verdicts, the CSV columns and a pipeline recipe are in the guide.
Check the servers you run
The same ids can be checked against a host. Run this on the machine itself, not on the laptop that deploys to it: it reads installed packages (dpkg, rpm or apk), snaps, the hardware (maker, model, firmware), the running container images with their operating system and packages, and the kernel version, compares them on the spot, and only the CVE ids leave the machine; the inventory stays on it, in ~/.lattice-scan. Naming the CVEs needs no key. Do it on each server after a deployment, and again when a new entry lands.
lattice-scan --cve CVE-2026-90817 --cve CVE-2024-10441 --cve CVE-2026-90436 --cve CVE-2026-115731 --cve CVE-2026-40217A match is a candidate for a person to confirm, not a finding. A distribution can fix a CVE under an unchanged version number, so a match is a candidate; on Debian-family hosts the report also shows whether the package's own changelog names the CVE. By default it opens the images your containers are running and reads their operating system and package list; a deep scan (--deep, a few minutes) opens every local image and the Python, Node, Java and Ruby packages inside them; for what an image declares, use the project check on its Dockerfile.
Guide: namiq.io/lattice/guides/choose-your-channel. MCP server (io.namiq/lattice in the MCP registry): namiq.io/lattice. Package: pypi.org/project/lattice-scan, or namiq.io/apt.
- Which way into Lattice fits your job →The command line, the Claude skill or the MCP server: what each needs, what works without a key and how to read the result.
- Lattice, the MCP server →The public graph the command reads, for AI agents over MCP.
- Install and connect →The signed apt repository, the fingerprint, and the connection commands for each client.
What we do not know yet
- Who is using these flaws, and how often. CISA names no attacker and we do not guess one. Ransomware use is as CISA records it; "unknown" means not recorded.
- EPSS is recalculated daily; the figures are as at 20 November 2026 and will have moved. The order is a rule on CISA's dates and EPSS, not a verdict on your estate: check what you run first.
- The bottom line, how the week connects, the first hour, who can skip it and the message are our interpretation of the records, not a statement by CISA or the vendors.