Data Security

Opensolr Data Security — find answers to your questions

CVE-2026-129474: PHP 8.5 use-after-free in magic method back...

CVE-2026-129474 is a memory safety flaw in PHP 8.5. A fatal error raised at the wrong moment inside a magic method call can corrupt memory and, in the worst case, run code sent by a remote attacker. It was published on November 19, 2026, and Opensolr has been protected against it since that same day.

01 · At a glance

Identifier
CVE-2026-129474
Severity
9.2 Critical (CVSS v4.0)
Published
November 19, 2026
Affected
PHP 8.5.0 to 8.5.12
Fixed in
PHP 8.5.13
Opensolr
Protected since November 19, 2026
Last reviewed
November 20, 2026

02 · What it is

When PHP builds a backtrace it collects the arguments of every call on the stack. For a call handled by __call() or __callStatic(), PHP 8.5 can read values that already point to freed memory.

If a fatal error, such as running over memory_limit, is raised while the application is entering such a call, the backtrace written for that error touches the stale values. A remote attacker who controls enough of the request to steer memory allocation can crash the PHP worker or corrupt its memory. With knowledge of memory addresses, arbitrary code execution is possible.

03 · Who is affected

A server is exposed only when all of the following are true:

  • It runs PHP 8.5.0 to 8.5.12.
  • fatal_error_backtraces is on. That is the default.
  • zend.exception_ignore_args is off. The development php.ini leaves it off; php.ini-production turns it on.
  • The application uses magic methods. Most frameworks and ORMs do.

04 · How to fix it

Upgrade to PHP 8.5.13 or later, then restart PHP-FPM or the web server so the running workers use the new build.

php -v
sudo apt update && sudo apt install --only-upgrade 'php8.5*'
sudo systemctl restart php8.5-fpm

05 · How to mitigate until you can upgrade

Turn argument collection off. The PHP advisory states that this setting prevents the flaw. Set it in the php.ini of the web SAPI (PHP-FPM or mod_php), not only in the command line one, then reload.

zend.exception_ignore_args = On

Backtraces keep their file names and line numbers. They only stop listing function arguments, which also keeps passwords and tokens out of your logs.

06 · How to check a server

php-fpm8.5 -v | head -1
php-fpm8.5 -i | grep -E 'zend.exception_ignore_args|fatal_error_backtraces'

The command line and PHP-FPM read different php.ini files. Check the one that serves web requests.

07 · Opensolr and this vulnerability

Status on November 20, 2026. Opensolr is protected against CVE-2026-129474. The condition it needs was closed on the platform on November 19, 2026, the day the advisory was published. Nothing is required from you: your Opensolr Index, your account and your data are not exposed to it.

  • Opensolr watches newly published vulnerabilities for every component of the platform, around the clock.
  • Each advisory is assessed against the platform as soon as it is published.
  • The fix is applied, or the vulnerable condition is closed, and the result is verified before the case is closed.

More on how Opensolr protects your data: Opensolr Trust Center and all security pages. Questions about a vulnerability that is not listed: contact Opensolr.

Official advisory: PHP security advisory GHSA-8mjj-2r7p-4hg2 · NVD entry.

Read Full Answer

CVE-2026-126714: PHP session files overwritten in part can l...

CVE-2026-126714 affects PHP applications that store sessions in files, which is the PHP default. A session write that is cut short can leave a file that PHP later reads back as injected objects. It was published on November 19, 2026, and Opensolr has been protected against it since that same day.

01 · At a glance

Identifier
CVE-2026-126714
Severity
9.2 Critical (CVSS v4.0)
Published
November 19, 2026
Affected
PHP 8.2 before 8.2.36, 8.3 before 8.3.37, 8.4 before 8.4.28, 8.5 before 8.5.13
Fixed in
PHP 8.2.36, 8.3.37, 8.4.28 and 8.5.13
Opensolr
Protected since November 19, 2026
Last reviewed
November 20, 2026

02 · What it is

The files session handler writes updated session data into the existing session file without emptying it first. If the write is interrupted, the file holds the start of the new session followed by the tail of the old one.

When PHP reads that file again, bytes that were part of an ordinary string can be unserialized as objects. An attacker who can influence session data, for example through session upload progress, and interrupt a write at the right point can inject objects. If the application contains a usable gadget chain, that becomes code execution. Without one, the result is a corrupted session.

03 · Who is affected

  • The server runs an affected PHP version.
  • The application uses native PHP sessions.
  • session.save_handler is files. That is the default.

Applications that keep sessions in a database, in Redis or in Memcached through their own handler do not use the vulnerable code path.

04 · How to fix it

Upgrade to PHP 8.2.36, 8.3.37, 8.4.28 and 8.5.13, depending on your branch, and restart PHP-FPM or the web server.

php -v
sudo apt update && sudo apt install --only-upgrade 'php8.*'
sudo systemctl restart php8.4-fpm

05 · How to mitigate until you can upgrade

Move sessions off the files handler. With the Memcached or Redis extension installed, two lines in php.ini are enough. Existing sessions end, so visitors sign in again once.

session.save_handler = memcached
session.save_path = "127.0.0.1:11211"
session.save_handler = redis
session.save_path = "tcp://127.0.0.1:6379"

If the application does not use upload progress, switching it off removes the easiest way to place data in a session:

session.upload_progress.enabled = Off

06 · How to check a server

php-fpm8.4 -i | grep -E '^session.save_handler|^session.save_path|^session.upload_progress.enabled'
ls /var/lib/php/sessions | head

A pool or a virtual host can override the handler, so check the values the application actually runs with.

07 · Opensolr and this vulnerability

Status on November 20, 2026. Opensolr is protected against CVE-2026-126714. The condition it needs was closed on the platform on November 19, 2026, the day the advisory was published. Nothing is required from you: your Opensolr Index, your account and your data are not exposed to it.

  • Opensolr watches newly published vulnerabilities for every component of the platform, around the clock.
  • Each advisory is assessed against the platform as soon as it is published.
  • The fix is applied, or the vulnerable condition is closed, and the result is verified before the case is closed.

More on how Opensolr protects your data: Opensolr Trust Center and all security pages. Questions about a vulnerability that is not listed: contact Opensolr.

Official advisory: PHP security advisory GHSA-fm2m-fjf5-v3cp · NVD entry.

Read Full Answer

CVE-2026-129291: PHP-FPM use-after-free with catch_workers_o...

CVE-2026-129291 is a flaw in the PHP-FPM master process. Code that already runs inside a PHP-FPM worker can use it to crash the master or to run code with the master's privileges, which are usually root. It was published on November 19, 2026, and Opensolr has been protected against it since that same day.

01 · At a glance

Identifier
CVE-2026-129291
Severity
8.8 High (CVSS v4.0)
Published
November 19, 2026
Affected
PHP 8.2.7 up to 8.2.35, 8.3 before 8.3.37, 8.4 before 8.4.28, 8.5 before 8.5.13
Fixed in
PHP 8.2.36, 8.3.37, 8.4.28 and 8.5.13
Opensolr
Protected since November 19, 2026
Last reviewed
November 20, 2026

02 · What it is

With catch_workers_output on, the PHP-FPM master reads what each worker writes to its output through a pipe and an event registered on it. When a worker exits, the master can close that pipe without removing the event, and a delayed cleanup can free the worker record while the event is still registered.

A later event is then dispatched through a pointer into freed memory. This is a local privilege escalation: the attacker must first be able to run PHP code in a worker. From there the master can be crashed or taken over.

03 · Who is affected

  • The server runs PHP-FPM in an affected version.
  • catch_workers_output is yes in at least one pool. It is off by default, but the official PHP-FPM Docker images turn it on.
  • The event mechanism is epoll, the default on Linux.

04 · How to fix it

Upgrade to PHP 8.2.36, 8.3.37, 8.4.28 and 8.5.13, depending on your branch, then restart PHP-FPM. A reload is not enough: the master process itself must be replaced.

sudo apt update && sudo apt install --only-upgrade 'php8.*'
sudo systemctl restart php8.4-fpm

05 · How to mitigate until you can upgrade

Turn worker output capture off in every pool. So that no PHP error is lost, give each pool its own error log first.

; /etc/php/8.4/fpm/pool.d/www.conf
catch_workers_output = no
php_admin_flag[log_errors] = on
php_admin_value[error_log] = /var/log/php8.4-fpm-www.log
sudo touch /var/log/php8.4-fpm-www.log
sudo chown www-data:www-data /var/log/php8.4-fpm-www.log
sudo php-fpm8.4 -t && sudo systemctl restart php8.4-fpm

06 · How to check a server

grep -rn '^catch_workers_output' /etc/php/*/fpm/pool.d/
grep -rn 'error_log' /etc/php/*/fpm/pool.d/

No output from the first command means the setting is at its default, off.

07 · Opensolr and this vulnerability

Status on November 20, 2026. Opensolr is protected against CVE-2026-129291. The condition it needs was closed on the platform on November 19, 2026, the day the advisory was published. Nothing is required from you: your Opensolr Index, your account and your data are not exposed to it.

  • Opensolr watches newly published vulnerabilities for every component of the platform, around the clock.
  • Each advisory is assessed against the platform as soon as it is published.
  • The fix is applied, or the vulnerable condition is closed, and the result is verified before the case is closed.

More on how Opensolr protects your data: Opensolr Trust Center and all security pages. Questions about a vulnerability that is not listed: contact Opensolr.

Official advisory: PHP security advisory GHSA-jm4m-qfqx-967m · NVD entry.

Read Full Answer

Loading more articles...