Skip to content
Security

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

·5 min read

The bottom line

All three records describe flaws that require no attacker login. Two score at the maximum of 10; the third scores 9.9. The one question that sorts them: do you run WP Libre Form on WordPress, Apache Juneau, or TPC Software Matchpoint?

757 CVE records were published in the last 30 hours. 90 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, 6 November 2026: 3 new critical CVEs worth readingFree analysis report · 7 pagesDaily CVE highlight, 6 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
Unknown WP Libre Form (CVE-2026-118423)10 (CVSS 3.1)See the noteOur note, below
Apache Software Foundation Apache Juneau (CVE-2026-121489)10 (CVSS 4.0)Apache Juneau 9.2.1, as stated in the CVE record.Our note, below
TPC Software Matchpoint (CVE-2026-111489)9.9 (CVSS 4.0)The vendor statement in the record recommends installing 'the latest available version' but does not name a version number.Our note, below

Unknown WP Libre Form, CVE-2026-118423

Anyone running WP Libre Form 1.5.0.1 should disable or remove the plugin immediately. The record names no fixed version; contact the author and wait for a patch before reinstalling.

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

An unauthenticated visitor can upload a PHP file through WP Libre Form's submission feature and run it on the server, gaining remote code execution. The record covers version 1.5.0.1. The record states no limiting condition.

Apache Software Foundation Apache Juneau, CVE-2026-121489

Check whether DirectoryResource's view, upload, or delete settings are enabled. If any are on, upgrade to 9.2.1 immediately — the record names it as the fix. If all are off, upgrading is still prudent; confirm which settings are active.

Score 10 (CVSS 4.0), published by Apache on 5 November 2026. Weakness: CWE-22.

An attacker who can reach Apache Juneau's DirectoryResource endpoint can escape its root directory and read, write, or delete any file the server process can access. The three enabling settings — view, upload, delete — are off by default.

TPC Software Matchpoint, CVE-2026-111489

Anyone running Matchpoint should contact TPC Software for the current release and install it. The record scores this 9.9. The vendor recommends updating but does not name a fixed version number.

Score 9.9 (CVSS 4.0), published by INCIBE on 5 November 2026.

A credential embedded in the Matchpoint mobile app can obtain the platform's authentication token without a password. The record says this grants unauthenticated access to API services. Exposure is highest where the API faces an untrusted network.

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-118423,CVE-2026-121489,CVE-2026-111489

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 names of running container images 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-118423 --cve CVE-2026-121489 --cve CVE-2026-111489

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 6 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