edoc Knowledge Base
German English
Auto Light Dark
Auto Light Dark
German English

Latest information on the PHP security vulnerabilities in the November release of PHP (2026-11-19)

Component

edoc 365 business process platform

Version

All versions

Created on

Last modified on

No Workflow Applied

Review status

No Workflow Applied

KB article number

2792882445

Summary

On 2026-11-19, updates were released for the supported PHP version branches, addressing several new PHP vulnerabilities. edoc has completed its assessment of the reported vulnerabilities.

There is no indication that an emergency update is necessary. The critical vulnerabilities in our software are either not exploitable—because the conditions required for exploitation are not met (for example, PHP-FPM is not in use)—or because the complexity of exploiting them is higher.

The fixes will be made available shortly as part of the regular release cycle in the following releases:

  • Monthly Release 2026/11.

  • New Quarterly hotfix Quarterly2026/Q3.3.

The review is complete. This Knowledge Base article will be updated as needed once the planned releases are made available.

Updates to this article

Date and time

Description

2026-11-20, 4:00 p.m.

  • Vulnerability assessment completed.

  • No indication was found that an emergency update is necessary.

  • Information about edoc automate has been added.

  • The fixes will be released as part of the regular release cycle with the Monthly Release 2026/11 and a new hotfix Quarterly 2026/Q3.3.

2026-11-19, 5:15 p.m.

  • Addendum to the preliminary information regarding the release of updated PHP images.

2026-11-19, 4:00 p.m.

  • Initial KB article.

  • Analysis of the reported PHP vulnerabilities has begun.

Current situation

edoc has completed its assessment of the published PHP vulnerabilities. There is currently no indication that an emergency update is required for our software.

Impact on edoc products

The critical vulnerabilities in our software are either not exploitable because the conditions for exploitation are not met—for example, PHP-FPM is not running—or the vulnerabilities are more complex to exploit.

For individual components (such as views in edoc automate), a vulnerability in the underlying PHP runtime (CVE-2026-126714) theoretically creates an attack surface when writing session data. However, since exploitation requires a targeted interruption of the storage process and complex technical prerequisites—regular use is by no means sufficient—we classify the risk as High (not Critical).

No exploitation has been confirmed to date. We recommend installing the patched PHP Runtime as soon as possible as part of your regular product updates.

As of today (2026-11-20), the fix will be included in the regular release cycle with the new monthly release, Monthly 2026/11, and a new Quarterly hotfix, Quarterly 2026/Q3.3.

An emergency update is not required once the assessment is complete. Until the regularly scheduled updates are installed, we continue to recommend limiting access to publicly accessible systems to only what is necessary.

Depending on your infrastructure, please verify whether access can be restricted to only the necessary networks, user groups, or upstream protection systems. These measures can reduce the attack surface but do not replace the installation of the provided security updates.

Planned actions by edoc

edoc has completed its technical assessment of the reported vulnerabilities. The results indicate that an emergency update is not necessary.

The necessary corrections are prepared and released as part of the regular release cycle:

  • Monthly 2026/11.

  • New Quarterly hotfix: Quarterly 2026/Q3.3.

Deployment of security updates

The updated versions are being released via the new Monthly 2026/11 and a new Quarterly hotfix Quarterly 2026/Q3.3. Customer systems should install the updates according to their update configuration or after manual approval.

  • Customer systems with automatic updates enabled receive available updates according to their update configuration.

  • For customer systems without automatic updates, provided updates must be installed manually.

Current status

  • The assessment of the PHP vulnerabilities is complete.

  • There is no indication that an emergency update is necessary.

  • Critical vulnerabilities in our software are either not exploitable because the conditions for exploitation are not met—for example, PHP-FPM is not running—or because the vulnerabilities are more complex to exploit.

  • The fixes will be released as part of the regular release cycle with the new Monthly release, Monthly 2026/11, and a new Quarterly hotfix, Quarterly 2026/Q3.3.

Last updated: