On this page (8 sections)
On October 27, 2026, the Debian Security Team published DSA-6589-1, a security update for php-mongodb, the MongoDB driver for PHP. The advisory covers three CVEs and says the flaws could result in denial of service.
If you run PHP applications on Debian 13 (trixie) that talk to MongoDB, this update is for you. The advisory is short and gives no technical detail, so this article explains what is known, what is not, and how to check and patch your servers.
At a glance
What Debian announced
The advisory, sent by Moritz Muehlenhoff on behalf of the Debian Security Team, says multiple vulnerabilities were discovered in the MongoDB driver for PHP and that they could result in denial of service. For the stable distribution, trixie, the problems are fixed in version 2.0.0-1+deb13u2, and Debian recommends upgrading php-mongodb packages.
The advisory lists three identifiers: CVE-2026-106432, CVE-2026-106436 and CVE-2026-112368. It does not say which flaw does what, how they are triggered, or how severe each one is. Debian points readers to its security tracker page for php-mongodb for per-release status.
What denial of service means for a PHP driver
The php-mongodb extension is the layer that lets PHP code open connections to MongoDB, send queries and decode the responses. A denial-of-service flaw in a component like this generally means an application can be made to crash, hang or consume excessive resources. Depending on how PHP is deployed, that could take down a worker process or degrade a site.
We cannot say from the advisory how these specific flaws are reached, for example whether through crafted application input or through data returned by a database server. Do not assume that a database on a private network makes you safe. Plan to patch regardless.
Who is realistically exposed
- Debian 13 (trixie) servers with the php-mongodb package installed.
- Sites and apps using MongoDB from PHP, such as custom applications, APIs, some CMS or e-commerce integrations and logging or session backends.
- Hosting providers and agencies that install the extension for many customers on shared or managed Debian hosts.
- Container images built on Debian trixie that include php-mongodb. Rebuild these, since updating the host does not change the image.
Servers that never installed php-mongodb from Debian packages are not covered by this advisory. The advisory also names only trixie, so other releases or distributions should follow their own vendors' notices.
How to check whether you are affected
This command lists the installed php-mongodb package and its version on Debian. It is read-only. If the version shown is older than 2.0.0-1+deb13u2 on trixie, you need to update. If it prints nothing, the package is not installed.
dpkg -l | grep php-mongodbThis command shows the installed version and the version apt would install from your configured repositories, which helps confirm the fixed build is available to you.
apt-cache policy php-mongodbThis command checks whether the MongoDB extension is loaded in the PHP command-line interpreter. Your web server may use a different PHP configuration, so also check the PHP-FPM or Apache setup you actually serve from.
php -m | grep -i mongodbWhat to do now
- Find every Debian host and container image that has php-mongodb installed.
- Run the version check above and compare against 2.0.0-1+deb13u2 on trixie.
- Update the package with apt (commands below), then restart PHP-FPM or your web server so the new extension is loaded.
- Rebuild and redeploy any container images based on Debian trixie that include php-mongodb.
- Re-run the version check and confirm the fixed build is installed.
- Watch the Debian security tracker for updates, such as severity details.
These commands refresh package lists and upgrade only the php-mongodb package to the newest version available from your configured Debian repositories. Afterward, confirm it reports 2.0.0-1+deb13u2 or newer on trixie.
sudo apt update
sudo apt install --only-upgrade php-mongodbAfter upgrading, restart the service that runs your PHP code. This read-only command lists PHP-FPM units so you can find the right service name for your PHP version.
systemctl list-units 'php*-fpm*'If PHP runs as an Apache module, this command restarts Apache so the updated extension is loaded. For PHP-FPM, restart the unit name found above in the same way.
sudo systemctl restart apache2Detection and monitoring afterwards
Since the stated impact is availability, watch for the symptoms: repeated PHP worker crashes, segmentation faults or out-of-memory kills in system logs, sudden spikes in response time, and error rates on pages that query MongoDB. Set uptime alerts on the pages and API endpoints that depend on the database so you notice a problem quickly. Our guide to uptime monitoring explains the basics, and Webforta Monitor can alert you when a site stops responding.
A web application firewall and rate limiting in front of public endpoints can reduce the impact of abusive request patterns in general, though we cannot say they would stop these particular flaws. See what a WAF is for what it can and cannot do.
Timeline
| Date | Event |
|---|---|
| 2026-10-27 | Debian publishes DSA-6589-1 with fixed php-mongodb 2.0.0-1+deb13u2 for trixie |
| Not stated | Discovery date, reporter and any exploitation reports are not given in the advisory |
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
