Security:Security Advisories/BSSA-2026-11: Difference between revisions

Created page with "{| class="wikitable" |+ ! ! |- |Date |2026-11-19 |- |Severity |reported "critical" (F5, CVSS 4.0: 9.2) / "high" (F5, CVSS 3.1: 8.1), BlueSpice assessment: '''critical''' (container <code>bluespice/proxy</code>, CVE-2026-123007), '''high''' (same, CVE-2026-123633), '''low''' (all other CVEs and containers, including the PHP vulnerabilities of 2026-11-19) |- |Affected | * Container <code>bluespice/proxy</code> in BlueSpice 5.1 up to 5.1.11 and 5.2 up to 5.2.7 (all editions..."
Tag: 2017 source edit
 
(No difference)

Latest revision as of 14:55, 19 November 2026

Date 2026-11-19
Severity reported "critical" (F5, CVSS 4.0: 9.2) / "high" (F5, CVSS 3.1: 8.1), BlueSpice assessment: critical (container bluespice/proxy, CVE-2026-123007), high (same, CVE-2026-123633), low (all other CVEs and containers, including the PHP vulnerabilities of 2026-11-19)
Affected
  • Container bluespice/proxy in BlueSpice 5.1 up to 5.1.11 and 5.2 up to 5.2.7 (all editions; contains nginx 1.31.6)
  • The container bluespice/wiki also contains a vulnerable nginx version, but does not use the affected features (not exploitable)
  • All other containers do not contain nginx and are not affected
  • PHP vulnerabilities of 2026-11-19: container bluespice/wiki in BlueSpice 5.1 and 5.2 contains a vulnerable PHP version (8.4.27), but is not exploitable in the default configuration
Fixed in
  • Container bluespice/proxy <version>. Use the mitigation below until then.
  • PHP vulnerabilities: BlueSpice 5.2.8 and 5.1.12 (PHP 8.4.28)
CVE

Problem

On 2026-11-18, the NGINX project published several vulnerabilities in the web server nginx (publicly known as "NGINX2Root"). Five of them are rated critical. They can corrupt the memory of an nginx worker process. An attacker can crash the process and may be able to run code on the server. Each vulnerability only applies if nginx uses a certain feature (HTTP/2, HTTP/3, mail proxy or name resolution in subrequests).

In BlueSpice, nginx runs in the reverse proxy (bluespice/proxy), which receives all requests from users and handles the encryption (HTTPS), and in the wiki container, behind the reverse proxy. The reverse proxy uses HTTP/2 by default.

On 2026-11-19, the PHP project published PHP 8.4.28 with fixes for several vulnerabilities. Five of them are rated critical. Each of them only applies if PHP runs with certain settings or the application uses certain features. In BlueSpice, PHP runs in the wiki container (bluespice/wiki) and in the collaborative editing service (bluespice/collabpads).

CVE Component Type of vulnerability BlueSpice 5
CVE-2026-123007 nginx HTTP/2 (container bluespice/proxy) Out-of-bounds write, remote code execution affected
CVE-2026-123633 nginx HTTP/2 (container bluespice/proxy) Use after free, possibly remote code execution affected
CVE-2026-121810 nginx HTTP/3 (container bluespice/proxy) Use after free not affected in default configuration
CVE-2026-123634 nginx resolver (container bluespice/proxy) Use after free not affected in default configuration
CVE-2026-113425 nginx mail proxy (container bluespice/proxy) Use after free not affected in default configuration
all five nginx (container bluespice/wiki) – not affected
CVE-2026-129496 PHP date/time functions (container bluespice/wiki) Use after free not affected in default configuration
CVE-2026-129289 PHP-FPM (container bluespice/wiki) Request smuggling, remote code execution not affected
CVE-2026-126714, CVE-2026-115560, CVE-2026-129481 PHP sessions (container bluespice/wiki) Deserialization of untrusted data, use after free not affected
all five PHP CVEs PHP (container bluespice/collabpads) – not affected

Impact assessment

CVE Assessment Mitigation without update
CVE-2026-123007 Critical. The reverse proxy is reachable from the internet and uses HTTP/2 by default. Network access to the server is enough; no login and no wiki rights are needed (like the PHP vulnerabilities in BSSA-2026-08). A public proof of concept shows code execution against nginx in a Docker container. An attacker who takes over the reverse proxy can read and change all traffic between users and the wiki, including passwords and session cookies, and can therefore take over any wiki account, including administrators. Switch off HTTP/2 in the reverse proxy (see below).
CVE-2026-123633 High. Also affects the reverse proxy in default configuration and needs no login. An attack is more difficult, because the attacker must first use up the connection capacity of the reverse proxy. Switch off HTTP/2 in the reverse proxy (see below).
CVE-2026-121810 Low. Only affects installations that enabled HTTP/3 (ENABLE_HTTP3=true) and published UDP port 443. This is not part of the standard setup. Keep HTTP/3 disabled (ENABLE_HTTP3=false, the default).
CVE-2026-123634, CVE-2026-113425 Low. The configuration of the reverse proxy does not use the affected features (name resolution in subrequests, mail proxy). Only custom nginx configuration added by the customer could make them reachable. None needed in the standard setup.
All five (container bluespice/wiki) Low (not affected). The nginx in the wiki container is only reachable from the internal network and does not use HTTP/2, HTTP/3, mail proxy or name resolution. It will be updated with the next regular release. None needed.
CVE-2026-129496 (PHP) Low. Only installations that set WIKI_LOG_LEVEL to warn or debug and get a PHP warning when the wiki container starts (for example because of an invalid time zone) are affected. In that case, an attacker without login could crash PHP processes and might be able to run code. Check the configuration (see below).
CVE-2026-129289, CVE-2026-126714, CVE-2026-115560, CVE-2026-129481 (PHP) Low (not affected). The wiki container does not use the affected PHP features: the web server does not reuse connections to PHP, the wiki does not store sessions in PHP session files, and session upload progress is disabled since BlueSpice 5.1.11.1 / 5.2.7.1. bluespice/collabpads runs PHP as a command-line server and is not affected. None needed. Installations older than 5.1.11.1 / 5.2.7.1 must be updated anyway, see BSSA-2026-08.

Solution

Fixed image not available yet A fixed bluespice/proxy image is in preparation. We will update this advisory when it is available. Until then, use the mitigation below.


Mitigation: switch off HTTP/2 in the reverse proxy

The setting ENABLE_HTTP2=false of the reverse proxy is not enough: the reverse proxy keeps HTTP/2 enabled for unknown host names if a default certificate exists, which is always the case with Let's Encrypt. Instead, replace the configuration template of the reverse proxy with a copy without HTTP/2.

Run these commands in the compose directory of bluespice-deploy. Use the bluespice-deploy script instead of plain docker compose, because only the script loads all required docker-compose.*.yml files.

./bluespice-deploy exec -T proxy cat /app/nginx.tmpl > proxy-nginx.tmpl.orig
sed '/^    http2 on;$/d' proxy-nginx.tmpl.orig > proxy-nginx-no-http2.tmpl
diff proxy-nginx.tmpl.orig proxy-nginx-no-http2.tmpl | grep -c '^<'

The last command must show 3. Then add the following to the file docker-compose.override.yml in the same directory (create the file if it does not exist; if it already has a services: section, add the proxy: part there):

services:
  proxy:
    volumes:
      - ./proxy-nginx-no-http2.tmpl:/app/nginx.tmpl:ro

Then run ./bluespice-deploy up -d. The reverse proxy is recreated; the wiki is unavailable for a few seconds.

To check that the mitigation is active, run:

  • ./bluespice-deploy exec proxy grep -c 'http2 on' /etc/nginx/conf.d/default.conf: must show 0
  • curl -sI --http2 https://wiki.example.com/ | head -1 (replace wiki.example.com with the host name of your wiki): must start with HTTP/1.1

The wiki keeps working; browsers use HTTP/1.1 instead of HTTP/2. If you have enabled HTTP/3 (ENABLE_HTTP3=true), disable it as well.

Remove the mount when you update The copied template belongs to the current version of the reverse proxy. When you install the fixed image, remove the proxy: part from docker-compose.override.yml and run ./bluespice-deploy up -d again, otherwise the new image keeps using the old template.


PHP: check the log level

The PHP update comes with the next regular release. Until then, only installations with a changed log level need to act. Run in the compose directory:

./bluespice-deploy logs wiki-web | grep 'PHP Startup'

If this shows warnings, remove the variable WIKI_LOG_LEVEL from your docker-compose.override.yml (or fix the cause of the warning, for example the time zone) and run ./bluespice-deploy up -d. If the command shows nothing, no action is needed.

If you suspect an attack

A public proof of concept exists (as of 2026-11-19). Repeated crashes of the reverse proxy can indicate attack attempts: ./bluespice-deploy logs proxy | grep 'exited on signal'. If you find such entries, follow the procedure in BSSA-2026-08. In addition, replace the TLS certificate and its private key, and have all users change their passwords, because the reverse proxy sees all traffic in plain text.