By Greg Nowak. Updated 19 November 2026.
Your vulnerability scanner flags Apache, but your hosting provider says it is patched. If you own the website or manage the client relationship, you need a clear answer: does this require a maintenance window, or can the finding be closed with evidence?
The Apache version number alone cannot settle that question. A reliable review connects the reported vulnerability to the package supplier, complete package revision, configuration and running service. That gives your team a defensible decision and a practical next step.
Apache 2.4.68 now needs a fresh review
Apache 2.4.68 is no longer the latest upstream security release. As of 19 November 2026, Apache’s official vulnerability list includes fixes in 2.4.69 and 2.4.71. Version 2.4.71, released on 11 November, fixes CVE-2026-119618, a critical memory-corruption vulnerability in mod_http2 that can lead to remote code execution. Apache lists upstream versions 2.4.55 through 2.4.70 as affected.
A record showing that the June fixes were installed therefore needs updating. For an upstream build, check subsequent Apache advisories. For a distribution package, check the supplier’s status for the exact operating-system release and package stream.
Why an older version can still be patched
Linux vendors often backport security fixes: they apply a correction to an older software branch without adopting every change in a newer upstream release. This helps preserve compatibility with existing applications and modules.
Red Hat explains this approach and why scanners that rely only on version numbers can produce false positives. The distribution revision matters as well as the familiar 2.4.x number.
However, “our vendor backports fixes” is the start of an investigation. Ask which advisory covers the reported CVE and which package revision contains its fix. Evidence for one vulnerability does not establish protection against later ones.
Use the evidence to choose the next action
| Evidence found | Decision | Next action |
|---|---|---|
| Supported vendor package contains the named fix | A version-based false positive is possible | Verify the running service, then document the advisory match |
| Installed revision is below the vendor’s fixed revision | An update is required for that finding | Assign an owner and schedule deployment |
| Updated package is installed, but old processes remain | Deployment is incomplete | Replace affected processes and verify service health |
| Configuration excludes the advisory’s prerequisites | The finding may be inapplicable | Record the conditions and reassess when configuration changes |
| Custom build or unknown package source | Patch status remains unproven | Obtain build evidence or plan a maintained replacement |
A practical Apache patch-review workflow
1. Identify what the scanner actually reached
Record the hostname, port, scan date and CVE identifiers. Establish whether the endpoint belongs to Apache itself, a reverse proxy or a service behind a load balancer. Check how many instances serve it.
Then identify the installation source: distribution package, third-party repository, container image or local compilation. Name the person responsible for applying updates and the person who will verify them. This prevents a finding from circulating between the agency, developer and hosting provider without an owner.
2. Capture complete package details
On Ubuntu or Debian, start with these read-only checks:
cat /etc/os-release
dpkg -l apache2 apache2-binSave the operating-system release, package status and complete revisions. Check that the packages are actually installed; a package database can also contain entries for removed software.
Ubuntu’s package-management guide explains package listings, repository configuration and dpkg -S /path/to/file, which identifies the package owning a particular file. Use the actual executable path when tracing an installation. Current repository settings alone do not establish where an existing binary originally came from.
3. Match each CVE to its advisory and configuration
Compare the full installed revision with the supplier’s fixed revision for that release and stream. Preserve distribution suffixes and use package-manager version comparison rules. Check that the operating system remains supported and that the server can access any required extended-support security channel.
Then examine the advisory’s prerequisites. Does it require HTTP/2, WebDAV, a particular proxy configuration or permission to edit .htaccess files?
Apache’s command reference documents -M for modules, -S for virtual-host settings and -t for configuration syntax. Use the installation’s wrapper, commonly apachectl or apache2ctl, with the service’s configuration and environment. These checks inspect the invoked binary and configuration; they do not certify existing workers.
4. Complete deployment in the running service
Before production changes, agree a maintenance window, rollback route and application checks. Installing a corrected package is only part of the job: the serving processes must use the corrected executable and libraries.
Follow the package supplier’s service-restart requirements. Apache’s restart documentation explains that graceful restarts and signal-based restarts retain the parent process. Do not assume a configuration reload replaces an updated executable. Verify process replacement and service health explicitly.
For containers, deploy a corrected image and replace every affected replica. Include all nodes behind the load balancer in verification.
5. Retest and write a useful conclusion
Repeat the scan from the original network position and test the business functions that depend on the site, such as forms, checkout or administration. If a banner-based alert persists, compare its detection method with the package and runtime evidence before deciding its status.
Keep the advisory links, package revisions, configuration assessment, deployment confirmation and retest results together. Give each finding a clear outcome: fixed, inapplicable under documented conditions, or open with an owner and deadline. Scope scanner exceptions to the evidence and review them when the installation changes.
Get the technical review to a clear handover
If the review spans your hosting provider, developers and security reviewer, Greg can help coordinate the evidence and remediation. Contact Greg about an Apache patch review with the scanner report and hosting details to establish what needs checking and who needs to act.
Related on GrN.dk
- Apache 2.4.68: What to Check Before You Call It Patched
- Apache 2.4.67: Why Legacy Reverse Proxies Belong Back on the Risk List
- Apache 2.4.68: Patch First, Then Audit Your Proxy Rules
Need help with this kind of work?
Discuss an Apache patch review with Greg Get in touch with Greg.