Skip to content
Security

Daily threat watch, 10 November 2026: 11 exploited CVEs added this week, 6 to act on now

·6 min read

The bottom line

CISA added 11 vulnerabilities to its exploited list from 5 November 2026 to 10 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, 2360 new CVE records were published in the last 30 hours, 444 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.

Cover page of Daily threat watch, 10 November 2026: 11 exploited CVEs added this week, 6 to act on nowFree analysis report · 7 pagesDaily threat watch, 10 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

At a glance

EntryActCISA dateFixed inEPSS
OpenBSD OpenSSH (CVE-2026-123158)TodayDue in 2 daysOpenSSH 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.17
SignalWire FreeSwitch (CVE-2026-116779)TodayDue in 2 daysFreeSWITCH 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)TodayDue in 2 daysIBM 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)TodayDue in 2 daysGPUStack 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)TodayDue in 3 daysESG firmware 9.4.0.030 (record); apply patch BNSF-40425 if running firmware 9.4.017 or above, or BNSF-40430 if below 9.4.017, per the vendor's advisory.0.02
Barracuda Networks Multiple Products (CVE-2026-111560)TodayDue in 3 daysESG: BNSF-40425 or BNSF-40430; ADC and WAF: BNADC-16586; Message Archiver: BNMA-32468; WAF Control Center: BNWF-60060; WSG: BNYF-24789. The advisory names patch IDs, not firmware version numbers.0.01
SonicWall SonicOS SSLVPN (CVE-2026-19868)Next patch cycleDue in 10 daysNot stated; see the note0.01
Cisco BroadWorks (CVE-2026-20320)Next patch cycleDue in 14 daysRI.2026.07 for all four components: Application Delivery Platform, Application Server, Profile Server, and Xtended Services Platform. Advisory first published 19 August 2026.0.00
Openwave Messaging Limited Webtop Media Transcoder (CVE-2026-111793)Next patch cycleDue in 14 daysThe record lists all versions before 1.1.22.0 as affected; 1.1.22.0 is the first version not listed as affected. The JVN advisory says to contact the developer for patch details.0.00
Microsoft Office (CVE-2026-124194)Next patch cycleDue in 14 daysOffice LTSC 2021: 16.0.14334.21048; Office LTSC 2024: 16.0.17932.21140. For Microsoft 365 Apps for Enterprise the record does not state a fixed build number.n/a
Google Chromium (CVE-2026-125350)Next patch cycleDue in 14 daysGoogle Chrome 157.0.8103.50. The CVE record names versions prior to this as affected. The source does not name a fixed version for Microsoft Edge or Opera.n/a

Do this today, in this order

In the next patch cycle

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-05" and .dateAdded <= "2026-11-10")
    | [.cveID,.dateAdded,.dueDate,.vendorProject,.product] | @tsv' | sort -k2

Run on 10 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-20320

Each 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-20320

A 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.

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 10 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.

Does this touch your business?

A new vulnerability is a question about what you run, who can reach it and what it would cost you. If you want a person to answer it for your own systems, start with your IT setup.

Also worth reading

Start with one piece of work.

Give us one piece of work and read access to one system. We map it and come back with what we found, what we would build and what it would take — before any commitment. You decide using our output, not our pitch.

Talk to us