Daily CVE highlight, 10 November 2026: 3 new critical CVEs worth reading
The bottom line
All three records score 10; none require valid credentials to exploit: one sends a crafted SAML assertion to SAP NetWeaver, one intercepts cleartext credentials from a GeoVision GV-Face, one connects using a fixed MQTT credential baked into D-Link M60 firmware. Which of these three products do you run?
2360 CVE records were published in the last 30 hours. 444 scored 8.5 or higher. 3 are below, chosen by a fixed rule: highest score first, then fewest conditions in the wording, one product each. None is on CISA's exploited list, so a score here is the record's author describing the worst case. Read the condition before you act on the number.
Free analysis report · 7 pagesDaily CVE highlight, 10 November 2026: 3 new critical CVEs worth readingThe 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 →At a glance
| Product | Score | Fixed in | Read next |
|---|---|---|---|
| SAP_SE SAP NetWeaver AS ABAP and ABAP Platform (SAML2 Service Provider) (CVE-2026-120017) | 10 (CVSS 3.1) | See the note | Technical Analysis |
| GeoVision Inc. GV-Face (CVE-2026-124600) | 10 (CVSS 4.0) | 2.2.2 (the record names this as unaffected; no vendor advisory could be read to confirm a release date) | Technical Analysis |
| D-Link M60 (CVE-2026-125086) | 10 (CVSS 4.0) | No unaffected or patched version is listed in the CVE record. The researcher's notes and the record name only firmware 1.12.B01; no source names a fixed release. | Technical Analysis |
SAP_SE SAP NetWeaver AS ABAP and ABAP Platform (SAML2 Service Provider), CVE-2026-120017
If you run SAP NetWeaver AS ABAP with the SAML2 SP enabled, act without delay. The record does not name a patched version; restrict network access to the ABAP stack until SAP issues one.
Score 10 (CVSS 3.1), published by Sap on 10 November 2026. Weakness: CWE-347.
The record says SAP NetWeaver AS ABAP does not verify SAML assertions sufficiently in certain configurations. An unauthenticated attacker can impersonate any user, including administrators. The limiting condition is that the SAML2 SP must be active.
GeoVision Inc. GV-Face, CVE-2026-124600
Anyone running an affected version of GV-Face should update to 2.2.2, which the record names as unaffected. If the update cannot be applied at once, isolate the device from untrusted network segments.
Score 10 (CVSS 4.0), published by GV on 10 November 2026. Weakness: CWE-319.
The record says GV-Face sends user credentials over unencrypted HTTP. An attacker who can intercept traffic on the network path can read those credentials without logging in. The record names 2.2.2 as unaffected.
D-Link M60, CVE-2026-125086
No patched firmware is named in the record or any source read. Block untrusted access to TCP port 1883 at the VLAN or firewall boundary until D-Link issues a fix for firmware 1.12.B01.
Score 10 (CVSS 4.0), published by VulDB on 10 November 2026. Weakness: CWE-798, CWE-259.
The record says firmware 1.12.B01 contains a fixed MQTT credential; a researcher's notes add that the device restores it on every boot, so an admin password change does not remove it. Any device on the same network reaching TCP port 1883 can connect using it.
Fifteen minutes this morning
- List the products above you run. If none, you are done.
- For each one you run, read the version from the product and compare it to the fixed version in the table.
- If it is in range, follow the note: reduce exposure first, then update.
- Book the update, and write down who owns it and by when.
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-120017,CVE-2026-124600,CVE-2026-125086Each 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-120017 --cve CVE-2026-124600 --cve CVE-2026-125086A 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
- These are new records. A record can change in the first days: scores, versions and wording are as at 10 November 2026. Nothing here has been tested.
- Exploitation is not recorded for any of them. That is not the same as none.
- The bottom line and the sentence under each product are our interpretation of the records and the vendors' pages, not a statement by the vendors.