Skip to content
Security

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

·5 min read

The bottom line

All three records describe remotely exploitable flaws where no named patched version exists and the attacker needs no prior access — or only a free or subscriber account. The question that sorts them: which of these three products is running in your environment right now?

879 CVE records were published in the last 30 hours. 218 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, 13 November 2026: 3 new critical CVEs worth readingFree analysis report · 7 pagesDaily CVE highlight, 13 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
Linksys EA8100 (CVE-2026-127275)10 (CVSS 4.0)See the noteTechnical Analysis
Jet Admin Cloud Platform (CVE-2026-123965)9.9 (CVSS 3.1)No fixed version is named in the record; remediation status is 'none available'. A source states mitigation via a sandbox component around 29 October 2026, but no release number is given.Technical Analysis
themagnifico52 Hotel Booking Lite (CVE-2026-125851)9.9 (CVSS 3.1)No official patch is available. The CVE record lists no unaffected version. Patchstack reported this on 11 November 2026 and states no patch exists.Technical Analysis

Linksys EA8100, CVE-2026-127275

No patched firmware is named. Block the router's management interface from the internet immediately. The exploit is public.

Score 10 (CVSS 4.0), published by VulDB on 12 November 2026. Weakness: CWE-306, CWE-287.

Two functions in the Linksys EA8100's JNAP API do not check who is calling. The record says a remote attacker can change remote-management and WiFi-warning settings without logging in. The exploit is public and the vendor did not respond.

Jet Admin Cloud Platform, CVE-2026-123965

No fixed version is named. Contact Jet Admin to confirm the October 2026 sandbox mitigation covers your deployment, then rotate all credentials held in .env files.

Score 9.9 (CVSS 3.1), published by Cisa-cg on 13 November 2026. Weakness: CWE-200.

Scored 9.9. A free Jet Admin account is enough for a remote attacker to expose the platform's .env files and extract the credentials in them. A source states a sandbox mitigation was applied around 29 October 2026; no release number is given.

themagnifico52 Hotel Booking Lite, CVE-2026-125851

No patch exists. If Hotel Booking Lite at 2.5.1 or earlier is installed, disable user registration immediately. The analysis notes this flaw type is used in mass-exploit campaigns targeting many sites.

Score 9.9 (CVSS 3.1), published by Patchstack on 13 November 2026. Weakness: CWE-434.

A subscriber-level WordPress account is enough to upload a PHP web shell to a site running Hotel Booking Lite at version 2.5.1 or earlier. This gives the attacker command execution using the web server's own permissions. No patch is named in the record.

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-127275,CVE-2026-123965,CVE-2026-125851

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-127275 --cve CVE-2026-123965 --cve CVE-2026-125851

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