Skip to content
Security

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

·5 min read

The bottom line

Three new high-scoring flaws, all fixed by the vendor. The one question that sorts them: does an attacker need to log in first? The STAGGS WordPress plugin flaw needs no account, so any site running it is exposed to anyone. The Quay and M365 Manager Plus flaws each need a valid login.

694 CVE records were published in the last 30 hours. 130 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, 12 November 2026: 3 new critical CVEs worth readingFree analysis report · 7 pagesDaily CVE highlight, 12 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
STAGGS (CVE-2026-78287)10 (CVSS 3.1)3.4.0, per the Patchstack advisory published 9 November 2026.Technical Analysis
Red Hat OpenShift Update Service (CVE-2026-110697)9.9 (CVSS 3.1)Red Hat Quay 3.9.28, 3.10.28, 3.12.24, 3.14.10, 3.15.9, 3.16.7, 3.17.7, or 3.18.3, per the vendor's advisory. Quay.io has already been fixed by Red Hat.Technical Analysis
Zohocorp M365 Manager Plus (CVE-2026-12591)9.9 (CVSS 3.1)M365 Manager Plus build 4818 (the vendor's advisory says it was fixed on 24 June 2026; builds 4817 and earlier are affected).Technical Analysis

STAGGS, CVE-2026-78287

Anyone running the STAGGS WordPress plugin should update to 3.4.0 now; 3.3.0 and earlier are affected. No login is needed, so treat it as urgent and first find which sites have it installed.

Score 10 (CVSS 3.1), published by Patchstack on 11 November 2026. Weakness: CWE-94.

A code-injection flaw lets an attacker run code on the web server without any account. It affects WordPress sites running the STAGGS plugin at version 3.3.0 or earlier. The record states no limiting condition.

Red Hat OpenShift Update Service, CVE-2026-110697

If you run no Quay or OpenShift registry, nothing to do. Anyone sharing one across teams should move to the patched build for their branch; the advisory lists fixes from 3.9.28 to 3.18.3.

Score 9.9 (CVSS 3.1), published by Redhat on 11 November 2026. Weakness: CWE-89.

An authenticated user crafts a namespace name whose wildcard character matches other tenants, then steals their robot-account tokens to read, push or overwrite their images. One limit: a basic account on a shared Quay or OpenShift registry is needed.

Zohocorp M365 Manager Plus, CVE-2026-12591

Running ManageEngine M365 Manager Plus? Upgrade to build 4818; 4817 and earlier are affected. The flaw needs a logged-in technician, so a server with no delegated technicians can wait.

Score 9.9 (CVSS 3.1), published by Zohocorp on 12 November 2026. Weakness: CWE-862.

A logged-in technician exploits weak permission checks in the delegated administration interface to gain rights beyond their role, leading to code execution on the server. It affects ManageEngine M365 Manager Plus, and needs a technician login.

Conditions the score may not show: authenticated.

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-78287,CVE-2026-110697,CVE-2026-12591

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-78287 --cve CVE-2026-110697 --cve CVE-2026-12591

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

  • These are new records. A record can change in the first days: scores, versions and wording are as at 12 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.

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