Skip to content
Security

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

·5 min read

The bottom line

These three records are unrelated: different products, different weaknesses. One question sorts them. Do you run Phoenix, the Station Launcher App in 3DEXPERIENCE, or Tensei with @tensei/auth? If not, you can stop reading.

389 CVE records were published in the last 30 hours. 66 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, 16 November 2026: 3 new critical CVEs worth readingFree analysis report · 7 pagesDaily CVE highlight, 16 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
Arize-ai phoenix (CVE-2026-53998)10 (CVSS 3.1)15.7.0. The record says it is fixed there. The release notes dated 13 May 2026 list 'prevent format-string injection in f-string template formatter'.Technical Analysis
Dassault Systèmes Station Launcher App in 3DEXPERIENCE platform (CVE-2026-93664)10 (CVSS 3.1)See the noteTechnical Analysis
tenseijs @tensei/auth (CVE-2026-129552)9.8 (CVSS 3.1)See the noteTechnical Analysis

Arize-ai phoenix, CVE-2026-53998

If you run Phoenix from 13.0.0 up to before 15.7.0, update to 15.7.0 this week; the record says it is fixed there. First check whether untrusted people can reach the service.

Score 10 (CVSS 3.1), published by GitHub on 16 November 2026. Weakness: CWE-134, CWE-200.

A crafted template sent to the applyChatTemplate query lets an attacker read server environment variables, including PHOENIX_SECRET, which the record says can lead to forged admin tokens. With authentication on, any account can reach it.

Dassault Systèmes Station Launcher App in 3DEXPERIENCE platform, CVE-2026-93664

If you use the Station Launcher App, ask Dassault Systèmes or your IT provider this week which release you run. The sources we read do not name a fixed release.

Score 10 (CVSS 3.1), published by 3DS on 16 November 2026. Weakness: CWE-502.

The record says untrusted serialised data in the Station Launcher App could let an attacker run their own code with no login. It gives no detail on how the attack is delivered. The record states no limiting condition.

tenseijs @tensei/auth, CVE-2026-129552

If you run Tensei with @tensei/auth, check today that JWT_SECRET is set, and set it if not. No fixed version is named, so do not wait for one. Treat past administrator activity as suspect.

Score 9.8 (CVSS 3.1), published by VulnCheck on 16 November 2026. Weakness: CWE-1394.

When JWT_SECRET is unset, @tensei/auth signs tokens with a key written in its code, so anyone can forge a token for any user, including an administrator. It only applies when JWT_SECRET is unset.

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-53998,CVE-2026-93664,CVE-2026-129552

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-53998 --cve CVE-2026-93664 --cve CVE-2026-129552

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