Short answer. Upstream Apache HTTP Server 2.4.41 is affected by more than 90 CVEs that the Apache project fixed in 2.4.42 and later releases. On Ubuntu 20.04 that number tells you very little. Canonical backports each fix into the same 2.4.41 source, ships it as a new package such as 2.4.41-4ubuntu3.23 or 2.4.41-4ubuntu3.23+esm11, and the Apache/2.4.41 (Ubuntu) banner never changes. To know whether you are exposed, compare the installed package version from dpkg -l apache2 with the fixed version on the Ubuntu CVE page or security notice (USN), then check which modules are actually loaded.
If a scanner flagged a host because its Server header reads Apache/2.4.41 (Ubuntu), this page is for you. It lists every CVE that the Apache project says affects 2.4.41, the condition each one needs, and the exact Ubuntu 20.04 package that fixes it. Then it shows how to check a real host in a few commands.
Key takeaways
- Ubuntu 20.04 (Focal Fossa) shipped
apache22.4.41 in April 2020 and has kept that upstream version for its whole life. Fixes arrive as2.4.41-4ubuntu3.Npackage revisions. - The last fix in the public archive is
2.4.41-4ubuntu3.23, published on 7 April 2025. Standard support for 20.04 ended on 31 May 2025. Every fix since then is an+esmNpackage that needs Ubuntu Pro. At the time of writing the newest is2.4.41-4ubuntu3.23+esm11(USN-9090-1, 12 November 2026). - CVE-2021-41773 and CVE-2021-42013, the famous path traversal pair, do not affect 2.4.41. Apache lists CVE-2021-41773 against 2.4.49 only and CVE-2021-42013 against 2.4.49 and 2.4.50, and Ubuntu marks 20.04 not affected by either.
- Two CVEs on this list are in the CISA Known Exploited Vulnerabilities catalog: CVE-2021-40438 (mod_proxy SSRF) and CVE-2024-38475 (mod_rewrite). Both are fixed in public 20.04 packages.
- As of 15 November 2026, one CVE that affects 2.4.41 has no 20.04 fix: CVE-2026-42528 in mod_dav, rated moderate. CVE-2019-17567 in mod_proxy_wstunnel is marked deferred.
- A fresh Ubuntu install does not load mod_proxy, mod_http2, mod_rewrite, mod_lua, mod_ssl or mod_dav. Most of the serious CVEs below need one of those.
Why your scanner says "Apache/2.4.41 (Ubuntu)"
The banner comes from two places. The version number is the upstream version compiled into the binary. The (Ubuntu) part comes from ServerTokens OS, which is what Ubuntu sets in /etc/apache2/conf-available/security.conf on 20.04. That same file sets ServerSignature On and TraceEnable Off.
Ubuntu does not move a stable release to a new upstream version for security fixes. It takes the patch from the Apache project, applies it to the 2.4.41 source, and bumps the Debian revision. The focal changelog shows the pattern clearly. 2.4.41-4ubuntu3.1 (August 2020) fixed five CVEs from the 2.4.44 release. 2.4.41-4ubuntu3.6 (September 2021) carried the CVE-2021-40438 fix and a regression follow-up for Unix domain socket URIs. 2.4.41-4ubuntu3.19 (July 2024) brought in the 2.4.60 fixes. None of these changed the string 2.4.41.
So a banner-matching scanner sees a server from August 2019 and reports every CVE published since. Some of those are fixed on the host. Some apply to modules that are not loaded. A few apply only to Windows builds. The job is to sort them.
We covered the general mechanics of backports for Debian, Ubuntu, Red Hat and Alpine in how to check whether a distro backported a security fix. The same problem with Ubuntu 20.04's nginx is in nginx 1.18.0 on Ubuntu.
The CVEs that matter most on 2.4.41
These are the ones worth reading about first: the two KEV entries, the request smuggling bugs that need nothing unusual, and the module bugs with critical CVSS scores.
CVE-2021-40438: mod_proxy SSRF (CISA KEV)
A crafted request uri-path can make mod_proxy forward the request to an origin server the attacker chooses. Apache rated it important and fixed it in 2.4.49. NVD scores it 9.0. CISA added it to the KEV catalog on 1 December 2021. It only matters if the host runs Apache as a reverse proxy with mod_proxy loaded. On 20.04 it is fixed in 2.4.41-4ubuntu3.6 (USN-5090-1). The first focal fix, in 3.5, broke some unix: socket proxy setups, which is why 3.6 exists. If you use ProxyPass to a Unix socket, make sure you are on 3.6 or later, not just 3.5. More detail in our CVE-2021-40438 write-up.
CVE-2024-38475 and CVE-2024-38474: mod_rewrite substitution flaws
CVE-2024-38475 is improper escaping of output in mod_rewrite. Substitutions in server context that use a backreference or variable as the first segment can map URLs to filesystem paths that were never meant to be reachable, which can lead to code execution or source disclosure. Apache rated it important, NVD scores it 9.1, and CISA added it to KEV on 1 May 2025. CVE-2024-38474 is the related encoded question mark issue. Both are fixed on 20.04 in 2.4.41-4ubuntu3.19 (USN-6885-1). The upstream fix made some unsafe rules fail unless they carry the new UnsafePrefixStat or UnsafeAllow3F flags. Ubuntu shipped a regression fix in 2.4.41-4ubuntu3.23 so that most rules work without UnsafeAllow3F, which is why Ubuntu's tracker lists 3.23 against CVE-2024-38474. See CVE-2024-38475 explained.
CVE-2023-25690: request smuggling through mod_rewrite and mod_proxy
Apache rated this important; NVD scores it 9.8. A configuration is affected when mod_proxy is enabled and a RewriteRule or ProxyPassMatch takes a non-specific capture from the request URL and puts it back into the proxied request target. A rule like the one below is the textbook case:
RewriteEngine on
RewriteRule "^/here/(.*)" "http://example.com:8080/elsewhere?$1" [P]
ProxyPassReverse "/here/" "http://example.com:8080/"
Fixed on 20.04 in 2.4.41-4ubuntu3.14 (USN-5942-1). If you cannot patch at once, narrow the capture so it cannot match spaces, carriage returns or line feeds, and avoid copying raw request data into the query string of a proxied URL.
CVE-2022-22720: request smuggling in any configuration
Apache 2.4.52 and earlier failed to close the inbound connection when an error occurred while discarding a request body. That opens the door to request smuggling. No special module is needed, so every 2.4.41 install before the fix was exposed. Fixed in 2.4.41-4ubuntu3.10 (USN-5333-1), along with CVE-2022-23943 (mod_sed out-of-bounds write, NVD 9.8) and two mod_lua issues.
CVE-2021-44790: mod_lua multipart overflow
A crafted request body can overflow a buffer in the mod_lua multipart parser used by r:parsebody(). The Apache team said it was not aware of an exploit. NVD scores it 9.8. It only applies if mod_lua is loaded and a Lua script calls r:parsebody. Fixed in 2.4.41-4ubuntu3.9 (USN-5212-1).
The HTTP/2 group
mod_http2 is not enabled on a fresh 20.04 install, but many sites turn it on. CVE-2024-27316 (CONTINUATION frames exhausting memory), CVE-2023-45802 (reset streams holding memory), CVE-2025-53020 (late memory release) and CVE-2026-57941 (use-after-free, NVD 9.8) all need it. The first two are fixed in public packages. The last two are in +esm2 and +esm8, so you need Ubuntu Pro to get them.
Ubuntu also backported newer mod_http2 code into 20.04 over the years. That has an odd side effect, covered in the next section but one: some HTTP/2 CVEs that Apache says start at 2.4.55 still got a 20.04 fix.
What changed in 2026
The Apache project shipped 2.4.66 in December 2025, then 2.4.67, 2.4.68, 2.4.69 and 2.4.71 through November 2026. Most of those CVEs reach back to 2.4.0, so they affect 2.4.41 too. The ones to read first if you run the matching module:
- CVE-2026-63292, a stack overflow in mod_vhost_alias triggered by the
Hostheader. Apache rated it moderate and says it can cause denial of service or possibly code execution. Fixed in+esm9(USN-8931-1). - CVE-2026-42535 and CVE-2026-93546, both in mod_dav_fs, reachable by WebDAV users with write access. Fixed in
+esm5and+esm9. - CVE-2026-24072 and CVE-2026-44119, where local
.htaccessauthors can read files with the privileges of the httpd user. Relevant on shared hosting. Fixed in+esm4and+esm5. - CVE-2026-106023, a mod_md NULL dereference fixed upstream in 2.4.71 on 11 November 2026. Ubuntu shipped the 20.04 fix a day later in
+esm11(USN-9090-1). - CVE-2026-42528, a mod_dav shared lock overflow where a user allowed to create WebDAV locks can crash child processes. Ubuntu's tracker shows 20.04 as "needed" with no package yet. If you run mod_dav, restrict who can lock.
Full CVE table for Apache 2.4.41 on Ubuntu 20.04
The list below comes from the Apache HTTP Server 2.4 vulnerabilities page. A CVE is included when its "Affects" range covers 2.4.41. The CVSS 3 score is the one shown on Ubuntu's CVE page, which matched NVD for every entry we spot-checked. "Needs" is the condition from Apache's own description. "Ubuntu 20.04 status" is from the Ubuntu CVE tracker as of 15 November 2026, and the USN is the first notice that covered 20.04.
Two notes on reading it. CVE-2020-9490 and CVE-2020-11993 are listed by Apache as affecting 2.4.20 to 2.4.43 in their descriptions, even though the version list on the same page skips 2.4.41. Ubuntu fixed both for 20.04. And "Pro only" means the fix shipped after standard support ended, so it is in the ESM archive that needs Ubuntu Pro.
| CVE | What it is | Apache rating | CVSS 3 | Needs | Ubuntu 20.04 status |
|---|---|---|---|---|---|
| CVE-2020-11984 | mod_proxy_uwsgi buffer overflow, possible RCE | Moderate | 9.8 | mod_proxy_uwsgi | Fixed in 2.4.41-4ubuntu3.1 (USN-4458-1) |
| CVE-2020-11993 | mod_http2 logging on wrong connection | Moderate | 7.5 | mod_http2 with trace or debug logging | Fixed in 2.4.41-4ubuntu3.1 (USN-4458-1) |
| CVE-2020-9490 | mod_http2 Cache-Digest crash | Important | 7.5 | mod_http2 with H2Push on (the default) | Fixed in 2.4.41-4ubuntu3.1 (USN-4458-1) |
| CVE-2019-17567 | mod_proxy_wstunnel tunnels non-upgraded connections | Moderate | 5.3 | mod_proxy_wstunnel | Deferred, no fix |
| CVE-2021-30641 | unexpected URL matching | Moderate | 5.3 | MergeSlashes OFF | Fixed in 2.4.41-4ubuntu3.3 (USN-4994-1) |
| CVE-2021-33193 | HTTP/2 method injection, request splitting | Moderate | 7.5 | mod_http2 plus mod_proxy | Fixed in 2.4.41-4ubuntu3.5 (USN-5090-1) |
| CVE-2021-34798 | core NULL dereference on malformed request | Moderate | 7.5 | any configuration | Fixed in 2.4.41-4ubuntu3.5 (USN-5090-1) |
| CVE-2021-36160 | mod_proxy_uwsgi out-of-bounds read | Moderate | 7.5 | mod_proxy_uwsgi | Fixed in 2.4.41-4ubuntu3.5 (USN-5090-1) |
| CVE-2021-40438 | mod_proxy SSRF via crafted uri-path (CISA KEV) | Important | 9.0 | mod_proxy reverse proxy | Fixed in 2.4.41-4ubuntu3.6 (USN-5090-1) |
| CVE-2021-44224 | forward proxy NULL dereference or SSRF | Moderate | 8.2 | ProxyRequests on | Fixed in 2.4.41-4ubuntu3.9 (USN-5212-1) |
| CVE-2021-44790 | mod_lua multipart parser overflow | Important | 9.8 | Lua scripts calling r:parsebody | Fixed in 2.4.41-4ubuntu3.9 (USN-5212-1) |
| CVE-2022-22719 | mod_lua uninitialized value in r:parsebody | Moderate | 7.5 | mod_lua | Fixed in 2.4.41-4ubuntu3.10 (USN-5333-1) |
| CVE-2022-22720 | request smuggling, connection not closed on body errors | Important | 9.8 | any configuration | Fixed in 2.4.41-4ubuntu3.10 (USN-5333-1) |
| CVE-2022-23943 | mod_sed out-of-bounds write | Important | 9.8 | mod_sed | Fixed in 2.4.41-4ubuntu3.10 (USN-5333-1) |
| CVE-2022-26377 | mod_proxy_ajp request smuggling | Moderate | 7.5 | mod_proxy_ajp | Fixed in 2.4.41-4ubuntu3.12 (USN-5487-1) |
| CVE-2006-20001 | mod_dav If: header out-of-bounds read or write | Moderate | 7.5 | mod_dav | Fixed in 2.4.41-4ubuntu3.13 (USN-5839-1) |
| CVE-2022-36760 | mod_proxy_ajp request smuggling | Moderate | 9.0 | mod_proxy_ajp | Fixed in 2.4.41-4ubuntu3.13 (USN-5839-1) |
| CVE-2022-37436 | backend truncates response headers | Moderate | 5.3 | mod_proxy with untrusted backend | Fixed in 2.4.41-4ubuntu3.13 (USN-5839-1) |
| CVE-2023-25690 | request smuggling via mod_rewrite and mod_proxy | Important | 9.8 | RewriteRule or ProxyPassMatch re-inserting URL data | Fixed in 2.4.41-4ubuntu3.14 (USN-5942-1) |
| CVE-2023-27522 | mod_proxy_uwsgi response splitting | Moderate | 7.5 | mod_proxy_uwsgi | Fixed in 2.4.41-4ubuntu3.14 (USN-5942-1) |
| CVE-2023-45802 | HTTP/2 reset stream memory held | Moderate | 5.9 | mod_http2 | Fixed in 2.4.41-4ubuntu3.15 (USN-6506-1) |
| CVE-2023-38709 | core response splitting from backends | Moderate | 7.3 | malicious backend or content generator | Fixed in 2.4.41-4ubuntu3.17 (USN-6729-1) |
| CVE-2024-27316 | HTTP/2 CONTINUATION memory exhaustion | Moderate | 7.5 | mod_http2 | Fixed in 2.4.41-4ubuntu3.17 (USN-6729-1) |
| CVE-2024-38473 | mod_proxy encoding, auth bypass | Moderate | 8.1 | mod_proxy with non-httpd access control | Fixed in 2.4.41-4ubuntu3.19 (USN-6885-1) |
| CVE-2024-38474 | mod_rewrite encoded question mark substitution | Important | 8.1 | mod_rewrite with unsafe backreferences | Fixed in 2.4.41-4ubuntu3.23 (USN-6885-1) |
| CVE-2024-38475 | mod_rewrite output escaping, code or source exposure (CISA KEV) | Important | 9.1 | mod_rewrite server-context rules | Fixed in 2.4.41-4ubuntu3.19 (USN-6885-1) |
| CVE-2024-38476 | malicious backend response headers, SSRF or script run | Important | 9.8 | backend apps behind httpd | Fixed in 2.4.41-4ubuntu3.19 (USN-6885-1) |
| CVE-2024-38477 | mod_proxy NULL dereference | Important | 7.5 | mod_proxy | Fixed in 2.4.41-4ubuntu3.19 (USN-6885-1) |
| CVE-2024-39573 | mod_rewrite hands URL to mod_proxy, SSRF | Moderate | 7.5 | mod_rewrite plus mod_proxy | Fixed in 2.4.41-4ubuntu3.19 (USN-6885-1) |
| CVE-2024-42516 | core response splitting via Content-Type | Moderate | 7.5 | app or backend that sets Content-Type | Fixed in 2.4.41-4ubuntu3.23+esm2 (USN-7639-2), Pro only |
| CVE-2025-23048 | mod_ssl TLS 1.3 resumption access bypass | Moderate | 9.1 | per-vhost client certificate trust | Fixed in 2.4.41-4ubuntu3.23+esm2 (USN-7639-2), Pro only |
| CVE-2025-49812 | mod_ssl TLS upgrade session hijack | Moderate | 7.4 | SSLEngine optional | Fixed in 2.4.41-4ubuntu3.23+esm2 (USN-7639-2), Pro only |
| CVE-2025-53020 | HTTP/2 late memory release DoS | Moderate | 7.5 | mod_http2 | Fixed in 2.4.41-4ubuntu3.23+esm2 (USN-7639-2), Pro only |
| CVE-2025-58098 | SSI passes query string to exec cmd | Moderate | 8.3 | SSI with mod_cgid | Fixed in 2.4.41-4ubuntu3.23+esm3 (USN-8338-1), Pro only |
| CVE-2025-66200 | mod_userdir plus suexec bypass | Moderate | 5.4 | .htaccess authors with FileInfo | Fixed in 2.4.41-4ubuntu3.23+esm3 (USN-8338-1), Pro only |
| CVE-2026-24072 | mod_rewrite ap_expr privilege escalation | Moderate | 8.8 | untrusted .htaccess authors | Fixed in 2.4.41-4ubuntu3.23+esm4 (USN-8396-1), Pro only |
| CVE-2026-33006 | mod_auth_digest timing attack | Moderate | 4.8 | mod_auth_digest | Fixed in 2.4.41-4ubuntu3.23+esm6 (USN-8589-1), Pro only |
| CVE-2026-34355 | mod_proxy_html buffer overflow | Moderate | 7.5 | mod_proxy_html with untrusted backend | Fixed in 2.4.41-4ubuntu3.23+esm5 (USN-8571-1), Pro only |
| CVE-2026-42535 | mod_dav_fs property database access | Moderate | 9.1 | WebDAV authors | Fixed in 2.4.41-4ubuntu3.23+esm5 (USN-8571-1), Pro only |
| CVE-2026-43951 | merge_response_headers out-of-bounds read | Moderate | 6.5 | mod_headers plus mod_mime, multiple languages | Fixed in 2.4.41-4ubuntu3.23+esm5 (USN-8571-1), Pro only |
| CVE-2026-44119 | .htaccess expressions read files as httpd user | Moderate | 5.5 | untrusted .htaccess authors | Fixed in 2.4.41-4ubuntu3.23+esm5 (USN-8571-1), Pro only |
| CVE-2026-44186 | mod_proxy_ftp infinite loop | Moderate | 7.3 | mod_proxy_ftp to attacker FTP server | Fixed in 2.4.41-4ubuntu3.23+esm5 (USN-8571-1), Pro only |
| CVE-2026-49975 | mod_http2 oversized allocation DoS | Moderate | 7.5 | mod_http2 | Fixed in 2.4.41-4ubuntu3.23+esm5 (USN-8398-4), Pro only |
| CVE-2026-42528 | mod_dav shared lock overflow | Moderate | 4.3 | users allowed to create WebDAV locks | Fix needed, none released yet |
| CVE-2026-57941 | mod_http2 use-after-free | Moderate | 9.8 | mod_http2 | Fixed in 2.4.41-4ubuntu3.23+esm8 (USN-8898-1), Pro only |
| CVE-2026-63292 | mod_vhost_alias stack overflow via Host header | Moderate | 7.5 | mod_vhost_alias | Fixed in 2.4.41-4ubuntu3.23+esm9 (USN-8931-1), Pro only |
| CVE-2026-93546 | mod_dav_fs namespace integer overflow | Moderate | 8.8 | WebDAV clients with write access | Fixed in 2.4.41-4ubuntu3.23+esm9 (USN-8931-1), Pro only |
| CVE-2026-106023 | mod_md NULL dereference | Important | n/a | mod_md | Fixed in 2.4.41-4ubuntu3.23+esm11 (USN-9090-1), Pro only |
Low-rated issues are grouped by the package that fixed them:
| Low-rated CVEs (Apache rating) | Ubuntu 20.04 status |
|---|---|
| CVE-2020-1927 (mod_rewrite open redirect); CVE-2020-1934 (mod_proxy_ftp uninitialized memory) | Fixed in 2.4.41-4ubuntu3.1 (USN-4458-1) |
| CVE-2020-13950 (mod_proxy_http NULL dereference); CVE-2020-35452 (mod_auth_digest one-byte stack overflow); CVE-2021-26690 (mod_session NULL dereference); CVE-2021-26691 (mod_session SessionHeader heap overflow) | Fixed in 2.4.41-4ubuntu3.3 (USN-4994-1) |
| CVE-2021-39275 (ap_escape_quotes buffer overflow) | Fixed in 2.4.41-4ubuntu3.5 (USN-5090-1) |
| CVE-2022-22721 (overflow with huge LimitXMLRequestBody) | Fixed in 2.4.41-4ubuntu3.10 (USN-5333-1) |
| CVE-2022-28614 (ap_rwrite read beyond bounds); CVE-2022-28615 (ap_strcmp_match read beyond bounds); CVE-2022-29404 (mod_lua r:parsebody denial of service); CVE-2022-30556 (mod_lua r:wsread information disclosure); CVE-2022-31813 (X-Forwarded-* headers dropped via Connection) | Fixed in 2.4.41-4ubuntu3.12 (USN-5487-1) |
| CVE-2023-31122 (mod_macro buffer over-read) | Fixed in 2.4.41-4ubuntu3.15 (USN-6506-1) |
| CVE-2024-24795 (response splitting in multiple modules) | Fixed in 2.4.41-4ubuntu3.17 (USN-6729-1) |
| CVE-2024-43204 (SSRF via mod_headers Content-Type); CVE-2024-47252 (mod_ssl log escaping); CVE-2025-49630 (mod_proxy_http2 assertion DoS) | Fixed in 2.4.41-4ubuntu3.23+esm2 (USN-7639-2), Pro only |
| CVE-2025-55753 (mod_md ACME retry timer overflow); CVE-2025-65082 (CGI environment variable override) | Fixed in 2.4.41-4ubuntu3.23+esm3 (USN-8338-1), Pro only |
| CVE-2026-28780 (mod_proxy_ajp heap overflow); CVE-2026-29169 (mod_dav_lock crash); CVE-2026-34059 (mod_proxy_ajp over-read and memory disclosure) | Fixed in 2.4.41-4ubuntu3.23+esm4 (USN-8396-1), Pro only |
| CVE-2026-34356 (ProxyPassReverseCookie overflow); CVE-2026-42536 (mod_xml2enc heap overflow); CVE-2026-44185 (mod_ssl OCSP stack over-read); CVE-2026-44631 (ap_regname heap underflow); CVE-2026-33007 (mod_authn_socache crash); CVE-2026-33523 (response splitting from backend status); CVE-2026-33857 (mod_proxy_ajp off-by-one reads); CVE-2026-34032 (mod_proxy_ajp over-read) | Fixed in 2.4.41-4ubuntu3.23+esm5 (USN-8571-1), Pro only |
| CVE-2026-29167 (mod_ldap per-dir use-after-free); CVE-2026-29170 (mod_proxy_ftp directory listing XSS) | Fixed in 2.4.41-4ubuntu3.23+esm6 (USN-8589-1), Pro only |
| CVE-2026-56154 (mod_rewrite lookahead use-after-free); CVE-2026-59797 (mod_ssl SSLRequire file functions in .htaccess) | Fixed in 2.4.41-4ubuntu3.23+esm8 (USN-8898-1), Pro only |
| CVE-2026-58415 (mod_dav_fs property read); CVE-2026-63045 (mod_proxy_ftp PASV address); CVE-2026-63686 (mod_xml2enc crash); CVE-2026-63718 (mod_proxy_uwsgi response smuggling); CVE-2026-73636 (mod_auth_digest nonce replay); CVE-2026-73637 (mod_auth_digest use-after-free); CVE-2026-79768 (mod_userdir information disclosure) | Fixed in 2.4.41-4ubuntu3.23+esm9 (USN-8931-1), Pro only |
| CVE-2026-46729 (mod_heartmonitor DoS); CVE-2026-47360 (mod_session_cookie cookie kept across redirect); CVE-2026-48005 (mod_auth_digest forced re-authentication); CVE-2026-56153 (mod_charset_lite heap overflow) | Fixed in 2.4.41-4ubuntu3.23+esm10 (USN-9016-1), Pro only |
Windows-only or not present on Ubuntu 20.04, per the Ubuntu tracker: CVE-2020-13938, CVE-2022-28330, CVE-2024-38472, CVE-2024-40898, CVE-2024-43394, CVE-2025-59775 and CVE-2026-59685 (all Windows only or code not present), plus CVE-2026-29168 (mod_md OCSP, marked not affected).
CVEs that do not affect 2.4.41, and a few surprises
Some well-known Apache CVEs show up in scanner output for 2.4.41 by mistake. Apache's own "Affects" ranges rule them out:
- CVE-2021-41773 and CVE-2021-42013 (path traversal and RCE): 2.4.49 and 2.4.50 only. Ubuntu marks 20.04 not affected and notes it never shipped the insufficient first fix. Background in our CVE-2021-41773 post.
- CVE-2021-41524 (HTTP/2 NULL dereference): 2.4.49 only.
- CVE-2021-31618 (HTTP/2): 2.4.47 only, a release that was never published.
- CVE-2025-54090 (
RewriteCond expralways true): 2.4.64 only. Not affected on 20.04. - CVE-2026-23918 (HTTP/2 double free): 2.4.66 only. Ubuntu marks releases before 26.04 not affected because the allocator change that turns the bug into a double free is not there.
- CVE-2026-42356 (internal redirects in CGI directories): 2.4.60 to 2.4.68. Not affected on 20.04.
Now the surprises. Because Ubuntu backported newer mod_http2 code and some newer core changes, a few CVEs that Apache scopes to later versions did reach 20.04, and Ubuntu fixed them there:
| CVE | Apache says | Ubuntu 20.04 fix |
|---|---|---|
| CVE-2022-30522 (mod_sed DoS) | 2.4.53 only | 2.4.41-4ubuntu3.12 (USN-5487-1) |
| CVE-2024-36387 (WebSocket over HTTP/2 crash) | 2.4.55 and later | 2.4.41-4ubuntu3.19 (USN-6885-1) |
| CVE-2024-39884 (handler source disclosure) | 2.4.60 only | 2.4.41-4ubuntu3.19 (USN-6885-1) |
| CVE-2024-40725 (handler source disclosure) | 2.4.60 to 2.4.61 | 2.4.41-4ubuntu3.21 (USN-6902-1) |
| CVE-2026-48913 (mod_http2 use-after-free) | 2.4.55 to 2.4.67 | 2.4.41-4ubuntu3.23+esm5 (USN-8571-1) |
| CVE-2026-56449 (mod_proxy_html crash) | 2.4.68 only | 2.4.41-4ubuntu3.23+esm10 (USN-9016-1) |
| CVE-2026-109163 (mod_vhost_alias one-byte overwrite) | 2.4.69 to 2.4.70 | 2.4.41-4ubuntu3.23+esm11 (USN-9090-1) |
| CVE-2026-119618 (mod_http2 heap corruption, critical) | 2.4.55 to 2.4.70 | 2.4.41-4ubuntu3.23+esm11 (USN-9090-1) |
CVE-2026-119618 is the one to notice. Apache rated it critical, with remote code execution in mod_http2, and Ubuntu's tracker notes that newer versions of the module were backported to stable releases. If you run HTTP/2 on 20.04, treat it as affecting you until you have +esm11. Version-range logic alone would have told you the opposite.
Why scanners raise false alarms on 2.4.41
There are three common causes.
- The banner is frozen.
Apache/2.4.41 (Ubuntu)is the same on a host that has never been updated and on one running+esm11. A check that reads theServerheader cannot tell them apart. - The module is not loaded. A fresh 20.04 install enables a short list of modules: authz_host, auth_basic, access_compat, authn_file, authz_user, alias, dir, autoindex, env, mime, negotiation, setenvif, filter, deflate, status and reqtimeout, on the event MPM. mod_proxy, mod_proxy_uwsgi, mod_proxy_ajp, mod_lua, mod_sed, mod_dav and mod_http2 are all off. A mod_lua CVE on a host without mod_lua is noise.
- The platform is wrong. Several CVEs on Apache's list are Windows only, or touch code that Ubuntu's build does not contain.
None of this means you can ignore the list. Hosts drift, people run a2enmod proxy and forget, and container images copy whatever config the base image had. It means you should check the package and the modules, not the banner.
For the wider picture on Ubuntu's notices and how to consume them in tooling, read how USN and OVAL data work.
How to check a real host
1. Get the installed package version
dpkg -l apache2 apache2-bin
apt-cache policy apache2
You want the full Debian version, for example 2.4.41-4ubuntu3.23+esm11. apt-cache policy also shows whether a newer candidate is waiting and which archive it comes from. If the candidate line points at an esm source, Ubuntu Pro is attached.
apache2 -v is less useful than it looks. It prints Server version: Apache/2.4.41 (Ubuntu) on every patched build.
2. Search the changelog for a CVE
zgrep -n "CVE-2021-40438" /usr/share/doc/apache2/changelog.Debian.gz
zgrep -c "CVE-" /usr/share/doc/apache2/changelog.Debian.gz
apt changelog apache2 | head -40
The installed changelog is the record of what your build contains. If the CVE ID appears in an entry at or below your installed version, the fix is in.
3. List the loaded modules
sudo apache2ctl -M | sort
ls /etc/apache2/mods-enabled/
Look for proxy_module, proxy_http_module, proxy_uwsgi_module, proxy_ajp_module, rewrite_module, http2_module, lua_module, sed_module, dav_module, dav_fs_module, ssl_module and vhost_alias_module. Each of those widens the list of CVEs that matter.
4. Let Ubuntu's tooling answer per CVE
pro status
pro fix CVE-2021-40438
pro fix CVE-2026-57941
pro fix checks whether the host is affected and, if a fix exists, tells you which package to install. For fixes after May 2025 it will say the update needs Ubuntu Pro if the machine is not attached.
5. See what the network sees
curl -sI https://your-host.example | grep -i '^server'
This is what the scanner read. It confirms the banner, nothing more.
6. Containers
Images built FROM ubuntu:20.04 keep whatever apache2 package was current at build time. Check the image, not the host:
docker run --rm --entrypoint dpkg your-image:tag -l apache2
docker run --rm --entrypoint sh your-image:tag -c 'zgrep -c CVE- /usr/share/doc/apache2/changelog.Debian.gz'
An image that has not been rebuilt since April 2025 cannot contain any +esm fix, whatever the host runs.
7. Fleet checks with OVAL
Canonical publishes OVAL data for 20.04 at security-metadata.canonical.com/oval/, including com.ubuntu.focal.usn.oval.xml.bz2. An OVAL-aware scanner compares installed package versions against fixed versions, which is the correct test. Note that OVAL for ESM fixes is only useful if the hosts can reach the ESM archive.
How to fix it
Patch the package and restart
sudo apt update
sudo apt install --only-upgrade apache2 apache2-bin apache2-data apache2-utils
sudo apache2ctl configtest && sudo systemctl restart apache2
Without Ubuntu Pro this takes you to 2.4.41-4ubuntu3.23. That covers everything in the table up to CVE-2024-39573 and the CVE-2024-38474 regression fix, but nothing from mid 2025 on.
Get the ESM fixes with Ubuntu Pro
Ubuntu 20.04 reached the end of standard support on 31 May 2025. With Ubuntu Pro, Canonical's expanded security maintenance for 20.04 runs to May 2030 and covers packages in the Main repository, which is where apache2 lives. Ubuntu Pro is free for personal use on up to five machines; commercial fleets need a subscription.
sudo pro attach YOUR_TOKEN
pro status
sudo apt update && sudo apt upgrade
After that, apt-cache policy apache2 should show an +esm candidate. Our post on Ubuntu 20.04 end of life, ESM and upgrade options goes through the choice in more depth.
Or move to a newer LTS
Ubuntu 22.04 ships Apache 2.4.52 (2.4.52-1ubuntu4.27 in the security pocket as of 12 November 2026) with standard support to May 2027. Ubuntu 24.04 ships Apache 2.4.58 (2.4.58-1ubuntu8.19) with standard support to May 2029. There is no direct upgrade from 20.04 to 24.04; you go through 22.04 or reinstall. The same banner problem follows you: a fully patched 24.04 host still says Apache/2.4.58.
Turn off modules you do not use
The cheapest fix for a module CVE is not loading the module.
sudo a2dismod lua sed proxy_uwsgi proxy_ajp proxy_ftp dav_fs dav
sudo a2dismod http2 # only if you do not serve HTTP/2
sudo apache2ctl configtest && sudo systemctl restart apache2
a2dismod will warn you about dependent modules. Read the warning before you confirm.
Interim mitigations while you schedule the patch
These reduce exposure; they are not substitutes for the package.
- CVE-2023-25690: rewrite proxy rules so captures cannot contain whitespace or control characters, for example
([^\s]*)style patterns, and avoid putting raw captures into a proxied query string. - CVE-2024-38475 and CVE-2024-38474: avoid server-context
RewriteRulesubstitutions that start with a backreference or variable. If the patched build breaks a rule, fix the rule rather than reaching forUnsafePrefixStat. - CVE-2021-40438 and CVE-2021-44224: keep
ProxyRequests Offunless you really run a forward proxy, and only proxy to fixed backends. - CVE-2020-9490: Apache's advisory says
H2Push offmitigates it on unpatched servers. - CVE-2026-42528: limit WebDAV locking to trusted users until Ubuntu ships a fix.
Hardening Apache 2.4.41 on Ubuntu
A short config pass removes the version leak and closes off some cheap attack paths. Directive names and defaults below are from the httpd 2.4 documentation. Put this in /etc/apache2/conf-available/security.conf or a new file you enable with a2enconf:
# Banner and error pages
ServerTokens Prod
ServerSignature Off
TraceEnable Off
# Request size. In 2.4.53 and earlier the default was 0 (unlimited),
# so set it explicitly on 2.4.41.
LimitRequestBody 10485760
# No directory listings under the document root
<Directory /var/www/>
Options -Indexes +FollowSymLinks
AllowOverride None
Require all granted
</Directory>
# Response headers (needs mod_headers: sudo a2enmod headers)
Header always set X-Content-Type-Options "nosniff"
Header always set X-Frame-Options "SAMEORIGIN"
Header always set Referrer-Policy "strict-origin-when-cross-origin"
Ubuntu's default apache2.conf enables Options Indexes FollowSymLinks on /var/www/, which is why the -Indexes override matters.
mod_status is on by default, but Ubuntu's status.conf limits /server-status with Require local. Keep it that way, or disable it:
<Location /server-status>
SetHandler server-status
Require local
</Location>
For TLS, 20.04 ships OpenSSL 1.1.1f, so mod_ssl can offer TLS 1.3. Ubuntu's default ssl.conf uses SSLProtocol all -SSLv3, which still allows TLS 1.0 and 1.1. Tighten it:
SSLProtocol -all +TLSv1.2 +TLSv1.3
SSLCipherSuite HIGH:!aNULL:!MD5
SSLHonorCipherOrder off
Hiding the version with ServerTokens Prod does not patch anything. It stops your banner from doing an attacker's reconnaissance for them, and it stops banner-only scanners from flooding your queue. More on that trade-off in Apache ServerTokens, TraceEnable and version leaks.
Patching the OS package is only half the story on most servers. The application behind Apache has its own dependencies, and those have their own fix gaps.
Fix it without waiting for upstream
Whatever the vulnerability, most of the risk sits in two gaps. The first is the time between a fix being published and that fix actually running in your production builds. The second, and worse, is the time before any fix exists at all, while a maintainer works out a patch and a release schedule. Waiting through both gaps is a habit, not a requirement. Safeguard gives teams three ways to close them.
1. Autonomous remediation: pull requests, not tickets
When a fixed version exists, Griffin, Safeguard's security model, opens a policy gated pull request that moves the affected dependency to the safe version, and your own CI runs your tests on it before anyone merges. You can run it on one repository or in bulk across every project that carries the vulnerable version. Remediation categories include dependencies, licenses, security posture and findings, and each one is set separately. Reachability analysis ranks the vulnerable code paths your application actually calls first, so the first pull requests you merge are the ones that matter most. Auto-merge is a separate switch and stays off by default, so your team decides what merges on its own and what still needs a human approval.
2. Gold Open Source: the safe version in seconds, free
gold.safeguard.sh is free and needs no login. Search any CVE or package to see affected and fixed versions, CVSS, EPSS, CISA KEV status and a recommended safe version, or use the "Am I affected?" checker. The same data is available through a free read API, README status badges and RSS threat feeds.
3. Gold Registry: start from components that are already fixed
Safeguard Gold rebuilds patched versions of open-source packages and images from source, signs each build, attaches an SBOM, SLSA provenance and VEX, and serves them from registry.safeguard.sh to your organization. Every Gold artifact is held continuously to zero exploitable critical or high CVEs and a completed license check, with signed build provenance (signed with Safeguard's key and verifiable with cosign, SLSA Build Level 3 as the design target) and a public evidence page you can hand to an auditor. An artifact loses its Gold badge if it regresses. Teams can point their own package directory at the registry so hardened equivalents resolve without changing how developers install anything.
When upstream has no fix yet, or will not ship one, Safeguard first works to get the fix accepted upstream. If the issue is severe or upstream will not move, Safeguard builds a fork, fixes the vulnerability there and publishes a hardened Gold build, so you are not stuck on a maintainer's release schedule. You can also request a hardened build of a specific package. Ask which packages it covers before you plan around it.
| Your situation | What to use |
|---|---|
| A fixed version exists | Autonomous remediation opens the upgrade pull request; Gold Open Source confirms the safe version |
| You need to know today whether you are affected | Gold Open Source lookup and "Am I affected?" checker, free and without login |
| You want vulnerable versions to stop shipping | Safeguard policies and gates in CI |
| Upstream has no fix yet, or will not ship one | A custom Gold request; fork and patch |
| You want to start clean on new projects | Pull hardened components and images from Gold Registry |
One honest limit: when the vulnerable code lives in a vendor appliance, a hosted service or an operating system runtime you do not build yourself, the fix still has to come from that vendor or distribution. The steps above apply to the open source dependencies and container images you build and ship, which is where most teams carry the largest and least tracked share of their exposure.
How Safeguard helps
The fix for banner noise is to check the distribution's fixed package version and whether the module is loaded, not the version string. Safeguard gives you the data to work that way.
Safeguard SCA inventories dependencies, including the packages inside container image layers, so an ubuntu:20.04 image with an old apache2 shows up with its real Debian version. Vulnerability data comes from NVD, GHSA, OSV, CISA KEV and vendor bulletins, which is what lets a finding be matched against Ubuntu's fixed version instead of the upstream range. Reachability analysis and prioritization, combining static, dynamic and config reachability with EPSS and KEV, ranks what actually matters: a KEV-listed mod_proxy bug on a host that loads mod_proxy sits above a mod_lua bug on one that does not.
Container image scanning covers registries such as Amazon ECR, Docker Hub, GCP Artifact Registry and other OCI registries. DAST tests the running web target. Policies and gates in CI stop an image built on an unpatched base from shipping in the first place.
FAQ
Is Apache 2.4.41 vulnerable?
Upstream 2.4.41 is affected by more than 90 published CVEs. An Ubuntu 20.04 package of 2.4.41 has a fix for all but two of them if it is on 2.4.41-4ubuntu3.23+esm11, and against everything published up to mid 2024 if it is on 2.4.41-4ubuntu3.23. The two without a 20.04 fix are CVE-2026-42528 (mod_dav, fix needed) and CVE-2019-17567 (mod_proxy_wstunnel, deferred). Check dpkg -l apache2.
Does Apache 2.4.41 have CVE-2021-41773?
No. CVE-2021-41773 affects 2.4.49 only, and CVE-2021-42013 affects 2.4.49 and 2.4.50. Ubuntu marks 20.04 not affected by both.
Why does my patched server still show Apache/2.4.41?
Ubuntu backports fixes into the 2.4.41 source and changes only the package revision. The Server header and apache2 -v report the upstream version, which stays 2.4.41.
Do I need Ubuntu Pro to patch Apache on 20.04?
For fixes released after 31 May 2025, yes. Those ship as +esm packages. The last fix in the free archive is 2.4.41-4ubuntu3.23 from April 2025.
Is CVE-2021-40438 fixed on Ubuntu 20.04?
Yes, in 2.4.41-4ubuntu3.6 (USN-5090-1). It only matters if mod_proxy is loaded.
How do I hide the Apache version on Ubuntu?
Set ServerTokens Prod and ServerSignature Off in /etc/apache2/conf-available/security.conf and reload Apache. That hides the version from the header and error pages; it does not change your patch level.
Sources
All accessed 15 November 2026.
- Apache HTTP Server 2.4 vulnerabilities
- Ubuntu security notices for apache2
- Ubuntu CVE-2021-40438
- Ubuntu CVE-2024-38475
- Ubuntu CVE-2026-42528
- Ubuntu CVE-2026-119618
- Ubuntu CVE-2021-41773
- USN-5090-1
- USN-6885-1
- USN-7639-2
- USN-9090-1
- apache2 focal changelog (2.4.41-4ubuntu3.23)
- apache2 package history on Launchpad
- NVD CVE-2021-40438
- NVD CVE-2023-25690
- NVD CVE-2024-38475
- NVD CVE-2021-44790
- CISA KEV catalog entry for CVE-2021-40438
- CISA KEV catalog entry for CVE-2024-38475
- Ubuntu release cycle
- Ubuntu 20.04 LTS support status
- Ubuntu Pro
- Ubuntu Pro Client: resolving CVEs with pro fix
- Apache core directives (ServerTokens, TraceEnable, LimitRequestBody)
- mod_ssl documentation
- mod_http2 documentation (H2Push)
- mod_proxy documentation (Unix domain sockets)
- Ubuntu focal apache2 security.conf
- Ubuntu focal apache2 default module list (postinst)