Daily CVE highlight, 7 November 2026: 3 new critical CVEs worth reading

The bottom line

THE BOTTOM LINE: All three records score 10 and require no prior login; they affect unrelated products with unrelated weaknesses. The question that separates them is whether a fix exists: only the Wanderer record names a fixed version.

844 CVE records were published in the last 30 hours. 164 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, 7 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

Microsoft Entra Device Registration, CVE-2026-109469

Anyone running Microsoft Entra Device Registration must act now. No fixed version is recorded. Confirm whether this service is reachable from untrusted networks and watch for Microsoft guidance.

Score 10 (CVSS 3.1), published by Microsoft on 6 November 2026. Weakness: CWE-639.

An unauthenticated network attacker can substitute a key they control for one Microsoft Entra Device Registration expects, bypass authorisation, and elevate their privileges. The record states no limiting condition.

• Our full note on CVE-2026-109469 →The vendor's advisory, who is exposed, what to do in order, a message to send your IT provider, and the analysis report.

Unknown WP Libre Form, CVE-2026-118423

Anyone running WP Libre Form 1.5.0.1 must act without delay. No fixed version is recorded; disable the plugin now and watch the vendor's channel for a patch.

Score 10 (CVSS 3.1), published by WPScan on 6 November 2026. Weakness: CWE-434 Unrestricted Upload of File with Dangerous Type.

An unauthenticated attacker can submit a form to WP Libre Form 1.5.0.1, upload a PHP file to a web-accessible location, and cause the server to execute it on request. The record states no limiting condition.

• Our full note on CVE-2026-118423 →The vendor's advisory, who is exposed, what to do in order, a message to send your IT provider, and the analysis report.

open-wanderer wanderer, CVE-2026-71495

Anyone running a self-hosted Wanderer instance below 0.20.0 should update to 0.20.0; the record names this as the fixed version. Check the PUBLIC_PRIVATE_INSTANCE setting while doing so.

Score 10 (CVSS 3.1), published by GitHub on 6 November 2026. Weakness: CWE-918.

On a Wanderer instance below 0.20.0, an unauthenticated attacker submits any URL to the trail download endpoint; the server fetches it and returns the result, exposing internal services. The record applies when PUBLIC_PRIVATE_INSTANCE is not set to true.

• Our full note on CVE-2026-71495 →The vendor's advisory, who is exposed, what to do in order, a message to send your IT provider, and the analysis report.

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-109469,CVE-2026-118423,CVE-2026-71495

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-109469 --cve CVE-2026-118423 --cve CVE-2026-71495

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.

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

• Today's mission →The vulnerabilities CISA says are already being exploited, in deadline order.
• The day's threat watch →What to do today, in order.