On this page (6 sections)
Debian published security advisory DSA-6620-1 on November 12, 2026, covering several vulnerabilities in the Apache HTTP server. According to the Debian security announcement, the flaws could result in remote code execution, denial of service and information disclosure.
If you run Apache from the Debian stable distribution (trixie), you should plan to update soon. The advisory is short and gives no per-CVE detail, so this article covers what is confirmed, what is not, and how to check and patch your servers.
What Debian announced
The advisory, signed by Salvatore Bonaccorso of the Debian security team, states that several vulnerabilities were discovered in the Apache HTTP server. It lists three CVE identifiers: CVE-2026-106023, CVE-2026-109163 and CVE-2026-119618. It also references Debian bug 1153732.
For trixie, the problems are fixed in apache2 version 2.4.71-1~deb13u1, and Debian recommends upgrading your apache2 packages. The advisory points to the Debian security tracker page for apache2 for the detailed status of each issue.
What we do not know yet
The advisory lists the overall impact classes but does not say which CVE causes which impact. The research available to us contains no CVSS scores, no description of the affected Apache modules or configurations, no mention of exploitation in the wild, and no details about older Debian releases. Only one publisher, Debian itself, is covered so far.
- Do not assume all three issues are remotely exploitable on every setup; the advisory does not map impact to individual CVEs.
- Do not assume that only default configurations are affected, or that they are not.
- Check the Debian security tracker for per-CVE status, as it is the place Debian points to for details.
Because remote code execution is named among the possible outcomes, treating this as a prompt to patch promptly is reasonable, even without a severity score.
Who is affected
The fix is stated for Debian stable (trixie). Servers that run the apache2 package from Debian trixie are the clear audience. Systems that build Apache from source, use a container image, or run another distribution's package are not covered by this advisory, and their status depends on their own vendor. Check the upstream Apache project and your distribution's tracker for those.
Web hosts, agencies and anyone with public-facing sites on Apache under Debian should look at this first. Debian does not say which configurations are affected, so check every server running the trixie apache2 package, regardless of its position in your architecture.
How to check your exposure
Run this on the server to see the installed apache2 package version and the candidate version from your configured repositories. You are up to date on trixie when the installed version is 2.4.71-1~deb13u1 or newer.
apt-cache policy apache2To confirm the running binary's version string as well, use the following read-only command. Note that Debian backports fixes into its package versions, so judge by the package version above rather than the upstream version number alone.
apache2 -vWhat to do now
- List your Debian servers that run apache2 and note their release (trixie or other).
- Refresh package lists and apply the apache2 update to version 2.4.71-1~deb13u1 or newer.
- Restart or reload Apache so the running process uses the fixed code.
- Re-run apt-cache policy apache2 to confirm the installed version.
- Review the Debian security tracker page for apache2 for per-CVE details and other releases.
- Check access and error logs for unusual requests or crashes around and before the update.
This command updates the package lists and upgrades only apache2 on Debian. Run it as root or with sudo.
sudo apt-get update && sudo apt-get install --only-upgrade apache2Validate the configuration, then restart the service so the new binary is loaded.
sudo apache2ctl configtest && sudo systemctl restart apache2Detection and monitoring afterwards
Since the advisory does not say whether exploitation has occurred, review your logs for the period before patching. Look for repeated server errors, unexpected process crashes or restarts of Apache, and requests that look unusual for your site. If you see signs of compromise, follow a recovery process such as website hacked: what to do.
For ongoing hygiene, keep automatic security updates enabled where it suits your change process, and track Debian security announcements. A free security headers check and regular scans of your public sites help you notice configuration drift, though they do not replace patching. A web application firewall can add a layer of filtering; see what is a WAF for what it can and cannot do.
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.
