Daily threat watch, 11 November 2026: 11 exploited CVEs added this week, 6 to act on now
The bottom line
CISA added 11 vulnerabilities to its exploited list from 6 November 2026 to 11 November 2026. 6 have a deadline within three days or already past. Read the exploited list first. It is the work list. Everything else is a reading list.
Separately, 2174 new CVE records were published in the last 30 hours, 436 of them scored 8.5 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, 11 November 2026: 11 exploited CVEs added this week, 6 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 (20): 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.
At a glance
| Entry | Act | CISA date | Fixed in | EPSS |
|---|---|---|---|---|
| OpenBSD OpenSSH (CVE-2026-123158) | Today | Due tomorrow | OpenSSH 10.6p2, released 5 November 2026. The vendor's advisory describes this as a workaround release; the root cause is stated to lie outside OpenSSH itself. | 0.19 |
| SignalWire FreeSwitch (CVE-2026-116779) | Today | Due tomorrow | FreeSWITCH 1.11.3, released 28 August per the vendor's release notes on GitHub. The record lists all versions below 1.11.3 as affected. | 0.02 |
| IBM Aspera Faspex (CVE-2026-123218) | Today | Due tomorrow | IBM Aspera Faspex 5.0.19 PL1 (Linux). The vendor's advisory says to validate that the faspex-core container image is at 5.0.19 (image id 1ce4b13, Fix Pack: 1). | 0.01 |
| GPUStack (CVE-2026-102895) | Today | Due tomorrow | GPUStack 2.2.0. The record says this issue is fixed in version 2.2.0. | 0.01 |
| Barracuda Networks Barracuda Email Security Gateway (ESG) (CVE-2026-116606) | Today | Due in 2 days | ESG 9.4.0.030 (first unaffected version per the CVE record); patch BNSF-40425 for ESG 9.4.017 and later; patch BNSF-40430 for ESG versions earlier than 9.4.017. | 0.09 |
| Barracuda Networks Multiple Products (CVE-2026-111560) | Today | Due in 2 days | Advisory patch IDs: ESG — BNSF-40425 (9.4.017+) or BNSF-40430 (<9.4.017); ADC and WAF — BNADCL-16586; BMA — BNMA-32468; WCC — BNWF-60060; WSG — BNYF-24789. | 0.06 |
| SonicWall SonicOS SSLVPN (CVE-2026-19868) | Next patch cycle | Due in 9 days | Not stated; see the note | 0.01 |
| Microsoft Office (CVE-2026-124194) | Next patch cycle | Due in 13 days | Office LTSC 2021: 16.0.14334.21048. Office LTSC 2024: 16.0.17932.21140. For Microsoft 365 Apps for Enterprise, the record does not give a specific fixed build number. | 0.02 |
| Google Chromium (CVE-2026-125350) | Next patch cycle | Due in 13 days | Google Chrome 157.0.8103.50. The record description states versions prior to this are affected. No source names a fixed version for Microsoft Edge or Opera. | 0.01 |
| Cisco BroadWorks (CVE-2026-20320) | Next patch cycle | Due in 13 days | RI.2026.07 for all four components: Application Delivery Platform, Application Server, Profile Server, and Xtended Services Platform. The vendor's advisory names this as the first fixed release. | 0.01 |
| Openwave Messaging Limited Webtop Media Transcoder (CVE-2026-111793) | Next patch cycle | Due in 13 days | The JVN advisory lists all versions before 1.1.22.0 as affected; 1.1.22.0 is the first version not listed as affected. Contact Openwave to obtain the patch — the advisory gives no further procedural details. | 0.01 |
Do this today, in this order
- OpenBSD OpenSSH, CVE-2026-123158, due tomorrow.
- SignalWire FreeSwitch, CVE-2026-116779, due tomorrow.
- IBM Aspera Faspex, CVE-2026-123218, due tomorrow.
- GPUStack, CVE-2026-102895, due tomorrow.
- Barracuda Networks Barracuda Email Security Gateway (ESG), CVE-2026-116606, due in 2 days.
- Barracuda Networks Multiple Products, CVE-2026-111560, due in 2 days.
- OpenBSD OpenSSH, CVE-2026-123158 →The full analysis, who is affected, and the analysis report.
- SignalWire FreeSwitch, CVE-2026-116779 →The full analysis, who is affected, and the analysis report.
- IBM Aspera Faspex, CVE-2026-123218 →The full analysis, who is affected, and the analysis report.
- GPUStack, CVE-2026-102895 →The full analysis, who is affected, and the analysis report.
- Barracuda Networks Barracuda Email Security Gateway (ESG), CVE-2026-116606 →The full analysis, who is affected, and the analysis report.
- Barracuda Networks Multiple Products, CVE-2026-111560 →The full analysis, who is affected, and the analysis report.
In the next patch cycle
- SonicWall SonicOS SSLVPN, CVE-2026-19868, due in 9 days.
- Microsoft Office, CVE-2026-124194, due in 13 days.
- Google Chromium, CVE-2026-125350, due in 13 days.
- Cisco BroadWorks, CVE-2026-20320, due in 13 days.
- Openwave Messaging Limited Webtop Media Transcoder, CVE-2026-111793, due in 13 days.
- SonicWall SonicOS SSLVPN, CVE-2026-19868 →The full analysis, who is affected, and the analysis report.
- Microsoft Office, CVE-2026-124194 →The full analysis, who is affected, and the analysis report.
- Google Chromium, CVE-2026-125350 →The full analysis, who is affected, and the analysis report.
- Cisco BroadWorks, CVE-2026-20320 →The full analysis, who is affected, and the analysis report.
- Openwave Messaging Limited Webtop Media Transcoder, CVE-2026-111793 →The full analysis, who is affected, and the analysis report.
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-06" and .dateAdded <= "2026-11-11")
| [.cveID,.dateAdded,.dueDate,.vendorProject,.product] | @tsv' | sort -k2Run on 11 November 2026 it printed 11 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-123158,CVE-2026-116779,CVE-2026-123218,CVE-2026-102895,CVE-2026-116606,CVE-2026-111560,CVE-2026-19868,CVE-2026-124194Each 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-123158 --cve CVE-2026-116779 --cve CVE-2026-123218 --cve CVE-2026-102895 --cve CVE-2026-116606 --cve CVE-2026-111560 --cve CVE-2026-19868 --cve CVE-2026-124194A 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 11 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.