SECURITY ADVISORIES

Security news you should act on.

Important vulnerabilities and patches for the software behind websites and business systems — PHP, Node.js, GitLab and more — explained clearly. Not sure if you’re affected? MetAI can check, fix and protect you going forward.

Last updated: Oct 23, 2026In JA · EN · ES
ADVISORIES

Latest security advisories

Newest first.

Oct 23, 2026PHPSeverity: MediumNo patch · workaround

New PHP vulnerability (no patch yet)

CVE-2026-115560

Remote code execution is possible only with an unusual combination of configuration and application code. PHP rates the risk as low and no attacks have been seen. Separate from php2shell.

Affected
Websites and apps running PHP
What to do
Set session.upload_progress.enabled = Off in php.ini (a fix will come in the next regular release)
MetAI website
Not affected
Read our article →
Oct 21, 2026PHPSeverity: CriticalPatch availableActively exploited

php2shell: critical PHP vulnerabilities

CVE-2026-109618 / 109619

Unauthenticated remote code execution (CVSS 9.2) affecting almost every PHP version from 5 to 8. Millions of attack attempts have been observed worldwide.

Affected
PHP 5–8 (PHP-FPM, Apache mod_php, php-cgi, LiteSpeed…)
What to do
Update to 8.5.12, 8.4.27, 8.3.36 or 8.2.35; end-of-life versions must be migrated
MetAI website
Not affected
Read our article →
Oct 21, 2026Node.jsSeverity: HighPatch available

Node.js October security release

10 CVEs (incl. CVE-2026-111497)

A Brotli decoder bug could allow remote code execution, plus flaws in TLS hostname checks and DNS.

Affected
Node.js 26.x, 24.x, 22.x (no fix for EOL lines such as 25)
What to do
Update to 26.12.1, 24.22.1 or 22.23.4; check Next.js, Express and Docker images too
MetAI website
Not affected
Read our article →
Oct 12, 2026GitLabSeverity: CriticalPatch available

Critical GitLab CE/EE vulnerability

CVE-2026-97229

A flaw in CI/CD regex handling allows code execution on the server (CVSS 10.0). Exploit code is public. gitlab.com users need not act.

Affected
Self-managed GitLab (19.2–19.4)
What to do
Update to 19.2.8, 19.3.4, 19.4.2 or later (check GitLab’s advisory for the latest)
MetAI website
Not affected
Read our article →
CHECKLIST

Six things to check today

01

Know what you run

List the versions of PHP, Node.js, WordPress, plugins and everything else your sites and systems run.

02

Retire end-of-life versions

End-of-life versions get no fixes, even for critical flaws.

03

Patch quickly

Attacks on critical flaws can start within hours of disclosure.

04

Close unused doors

Unpublish or remove admin panels, features and files you don’t use.

05

Block attacks automatically

Filters that block suspicious traffic and server-less setups make you a much harder target.

06

Keep backups

Back up your site and data regularly — and check you can actually restore them.

HOW WE HELP

How MetAI can help

Emergency check

We identify the software and versions behind your sites and apps and whether you are affected.

Fixes and updates

Safe updates for PHP, Node.js, WordPress and libraries, including migration from end-of-life versions.

Protection going forward

Attack filters, migration to server-less static sites and monitoring for suspicious traffic.

Sites built with MetAI Builder are hard targets from the start.

They are served as static sites with no PHP or database, and our own attack filter blocks suspicious requests automatically. None of the recent PHP or Node.js vulnerabilities affected the MetAI website.

See MetAI Builder

Not sure if you’re safe?

In a free 30-minute call we’ll look at your sites and systems.