Skip to content
Security

Daily CVE highlight, 31 October 2026: 3 new critical CVEs worth reading

·3 min read

The bottom line

Three unrelated products, each with a flaw that lets an attacker run commands or code on a server. The question that sorts them: do you run any of them? Only the invoice plugin needs no login; the other two need an account.

339 CVE records were published in the last 30 hours. 68 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, 31 October 2026: 3 new critical CVEs worth readingFree analysis report · 6 pagesDaily CVE highlight, 31 October 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
pgadmin.org pgAdmin 4 (CVE-2026-116241)9.9 (CVSS 3.1)pgAdmin 4 9.19. The record lists versions before 9.19 as affected. The tracking issue says the fix is pending for 9.19, and no source confirms a release.Our note, below
mqttsnet thinglinks (CVE-2026-62853)9.9 (CVSS 3.1)ThingLinks 1.4.0 (released 22 July 2026, per the project's release notes)Our note, below
addonsorg PDF Invoice for WooCommerce + Drag and Drop Template Builder (CVE-2026-109220)9.8 (CVSS 3.1)See the noteOur note, below

pgadmin.org pgAdmin 4, CVE-2026-116241

If you run pgAdmin 4, limit who can sign in now. Ask your IT provider to move to 9.19 once it is released. The tracking issue says the fix is pending; no release is confirmed.

Score 9.9 (CVSS 3.1), published by PostgreSQL on 30 October 2026. Weakness: CWE-78, CWE-115.

An ordinary database role can make pgAdmin's Import/Export tool run an operating-system command on the pgAdmin host, as the account running pgAdmin. The description ties it to standard_conforming_strings being off.

mqttsnet thinglinks, CVE-2026-62853

If you run ThingLinks, update to 1.4.0 this week. Before that, find out who can log in to it.

Score 9.9 (CVSS 3.1), published by GitHub on 30 October 2026. Weakness: CWE-78, CWE-94.

A logged-in user can send their own Groovy code to the rule engine's script endpoint, and the server runs it with no sandbox. The attacker needs a login, which the vendor's advisory says can be low-privilege.

Conditions the score may not show: authenticated.

addonsorg PDF Invoice for WooCommerce + Drag and Drop Template Builder, CVE-2026-109220

If you run this plugin, act today: check whether it is installed and which version. No fixed version is named in the sources, so do not assume one.

Score 9.8 (CVSS 3.1), published by Wordfence on 31 October 2026. Weakness: CWE-502.

The record says text in the checkout note field reaches code that rebuilds PHP objects without checks, so someone with no account can run code on the server. The record states no limiting condition.

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.

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 31 October 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