SUSE PHP security update: advisory 4603-1 and monitoring

SUSE PHP security update: advisory SUSE-SU-2026:4603-1 of 9 October 2026 fixes ten CVEs; PHP version inventory, metrics and patch tracking.
Faille PHP SUSE : avis 4603-1, versions et supervision

The SUSE PHP security update of 9 October 2026 is not a single fix: advisory SUSE-SU-2026:4603-1, “Security update for php8”, rated “important” by SUSE, fixes ten CVEs at once. Among them are a denial of service in the SOAP parser (CVE-2026-91765, CVSS score 7.5 at the NVD) and credential disclosure on redirects (CVE-2026-91766). If PHP runs in your estate, the real question is: on which machines, and in which version?

This article sticks to the CVEs whose description is confirmed by the NVD, then proposes an inventory and monitoring method. It does not replace the advisory: read it for your SUSE product. span.observer has not applied this fix or tested any exploitation.

SUSE PHP security update: what the 9 October 2026 advisory says

  • Advisory: SUSE-SU-2026:4603-1, published 9 October 2026, rated “important” (SUSE announcement page).
  • Content: ten CVEs referenced, from CVE-2025-1218 to CVE-2026-93682.
  • Affected products: specific to each advisory; read the announcement’s list for your SUSE Linux Enterprise version. Other php8 advisories exist for other products.

Six of the ten CVEs are described here according to the NVD (read on 22 October 2026, at least two with “Awaiting Analysis” status, so without final analysis):

  • CVE-2025-1218 (score 3.4): the mysqlnd protocol parser reads fields before checking packet size; a malicious or compromised MySQL server can cause an out-of-bounds read and crash the process.
  • CVE-2025-14181 (6.5): the SOAP HTTP client can suffer a heap buffer overflow if a check based on signed integer overflow is optimised away by the compiler.
  • CVE-2026-6103 (4.3): the Phar TAR parser wraps a poorly checked size; a crafted archive can inject entries.
  • CVE-2026-91765 (7.5): unbounded recursion in the SOAP XML parser; a deeply nested SOAP request can exhaust a SoapServer’s stack and crash the process.
  • CVE-2026-91766 (5.9): the http:// stream forwards Authorization, Cookie and Proxy-Authorization headers on a redirect to another host.
  • CVE-2026-91768 (6.5): the FastCGI client’s IPv6 check compares only 12 of 16 bytes, so listen.allowed_clients accepts a whole /96 prefix.

For CVE-2025-1218 and CVE-2026-91765, the NVD lists upstream PHP 8.2.34, 8.3.35, 8.4.26 and 8.5.11 as fixed versions. SUSE packages often backport fixes: compare the fix, not just the version number.

The other four CVEs in the advisory (CVE-2026-91767, -91769, -92842, -93682) are not detailed here, for lack of a confirmed description in what we read.

Finding PHP versions in production

A reliable inventory answers: which machine, which process, which version, which package. A few real commands:

# CLI binary version
php -v

# Loaded modules (soap, mysqlnd, phar, openssl)
php -m | grep -iE 'soap|mysqlnd|phar|openssl'

# Installed PHP packages (SUSE, RPM)
rpm -qa 'php8*'

# Patches available for a given CVE
zypper list-patches --cve=CVE-2026-91765

Caution: php -v describes the CLI binary, not necessarily the PHP-FPM or Apache module actually serving traffic. Also check php-fpm -v and containers, whose image may ship its own version. To see whether a SUSE package contains the fix, look for CVE identifiers in its changelog with rpm -q --changelog php8 | grep CVE-, if the package mentions them there.

Monitoring: metrics, patches, priorities

Turn the inventory into a metric. With node_exporter, the “textfile” collector reads .prom files from the directory set by --collector.textfile.directory. A scheduled script can write:

php_version_info{version="8.2.34",host="web-01"} 1

You then get the number of machines per version, the list of off-target machines and an alert when an unpatched version remains after a set delay. The same data can go out over OTLP to Dynatrace SaaS, Dynatrace Managed or another tool: see OpenTelemetry and Prometheus, complementary and Prometheus with Dynatrace on Kubernetes.

What priority to give?

  1. Exposure: a public SoapServer (CVE-2026-91765) comes before an internal script.
  2. Attack path: a PHP client connecting to a trusted MySQL (CVE-2025-1218) is less urgent than an Internet entry point.
  3. Score and analysis: CVSS scores help, but several CVEs still lack final analysis at the NVD.
  4. Fix delay: set an SLO, for example “95% of hosts patched within 14 days”, see choosing your SLIs.

For platform-side vulnerability detection, see Application Security and vulnerabilities; check the documentation for supported technologies before relying on it.

How to check that it works

  1. Apply the fix on a test machine with zypper, then restart PHP-FPM or Apache.
  2. Re-run the inventory: the expected package and version appear.
  3. Confirm the php_version_info metric reflects the change in your tool.

Best practices

  • Read the advisory for your exact product, not a neighbouring one.
  • Inventory containers and base images too.
  • Restart services after patching: an already loaded process keeps the old code.
  • Only cite a CVE with a description confirmed by a source.

Frequently asked questions

What does advisory SUSE-SU-2026:4603-1 fix?

It references ten CVEs for the php8 package; six are described above according to the NVD. See the announcement for the full list and products.

My PHP is 8.2.34: am I protected?

Not necessarily. The upstream version number is not enough on a distribution that backports: check the fixed package named in the advisory.

Do I need to restart after the update?

Generally yes: restart PHP-FPM or the web server so the new code is loaded.

Conclusion

This SUSE PHP security update is a reminder that an update without an inventory cannot be verified. Measure versions, set a fix deadline and track it like an SLO. Sources: advisory SUSE-SU-2026:4603-1 and the NVD.

span.observer is an independent community blog, not affiliated with SUSE, the PHP project or Dynatrace LLC. Trademarks belong to their owners. Information changes quickly: check it in the official advisory.

Total
0
Shares
Leave a Reply

Your email address will not be published. Required fields are marked *

Previous Post
PlayStation Plus octobre 2026 : jeux, SLO et statut

PlayStation Plus October 2026: games, SLOs and status

Next Post
SkillSpector scanner sécurité skills : installer et lire

SkillSpector agent skills security scanner: install and read

Related Posts