Skip to content
Security

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

·5 min read

The bottom line

3 new records scored 8.5 or higher and nothing says yet that anyone is using them. If you run any of these products, check the version today.

824 CVE records were published in the last 30 hours. 135 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.

Cover page of Daily CVE highlight, 4 November 2026: 3 new critical CVEs worth readingFree analysis report · 8 pagesDaily CVE highlight, 4 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

ProductScoreFixed inRead next
Qihoo 360 D621-2 (CVE-2026-121606)10 (CVSS 4.0)None. The researcher's disclosure states the flaw is present in all obtained firmware versions from 6.0.24 to 6.4.9 and that 6.4.9 remains unfixed.Our note, below
Qihoo 360 D603-2 (CVE-2026-121607)10 (CVSS 4.0)None. The researcher's notes state that firmware 6.4.9 — the most recent version tested — carries byte-identical vulnerable code to earlier releases.Our note, below
Qihoo 360 Whole Home Router M5 (CVE-2026-121609)10 (CVSS 4.0)See the noteOur note, below

Qihoo 360 D621-2, CVE-2026-121606

Anyone running a Qihoo 360 D621-2, D603-2, D600-2, D619, D606-6, or D706 camera on firmware 6.0.24 to 6.4.9 must act now: no fix exists and the exploit is public. Isolate the camera from untrusted networks immediately.

Score 10 (CVSS 4.0), published by VulDB on 4 November 2026. Weakness: CWE-347, CWE-345.

A word search of the record found none of the usual conditions (privileges, a logged-in user, a non-default setting, local network, physical access, a click). That is a search, not a reading, so read the record yourself before you rule it out.

Qihoo 360 D603-2, CVE-2026-121607

Owners of Qihoo 360 D603-2, D600-2, D606-6, D706 or D618_A cameras on firmware up to 6.4.9 must act now: no patch exists and a working exploit is public. Isolate the camera from any network segment an untrusted device can reach.

Score 10 (CVSS 4.0), published by VulDB on 4 November 2026. Weakness: CWE-78, CWE-77.

A word search of the record found none of the usual conditions (privileges, a logged-in user, a non-default setting, local network, physical access, a click). That is a search, not a reading, so read the record yourself before you rule it out.

Qihoo 360 Whole Home Router M5, CVE-2026-121609

Anyone responsible for a 360 Whole Home Router M5 or M50 on firmware 4.0.17.1566 must act now: no patch exists and the exploit is publicly available. Check whether each device has completed initial setup; if it has not, isolate it from the local network immediately.

Score 10 (CVSS 4.0), published by VulDB on 4 November 2026. Weakness: CWE-798, CWE-259.

A word search of the record found none of the usual conditions (privileges, a logged-in user, a non-default setting, local network, physical access, a click). That is a search, not a reading, so read the record yourself before you rule it out.

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-121606,CVE-2026-121607,CVE-2026-121609

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, 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-121606 --cve CVE-2026-121607 --cve CVE-2026-121609

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. It reads the names of the running images, not what is 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

  • These are new records. A record can change in the first days: scores, versions and wording are as at 4 November 2026. Nothing here has been tested.
  • Exploitation is not recorded for any of them. That is not the same as none.

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