By Greg Nowak. Updated 31 October 2026.
An inherited Apache reverse proxy can sit quietly between your customers and several generations of applications. It may handle checkout, a client portal or redirects from an old domain. When a security update arrives, installing the package is only part of the job. Someone also needs to know which services depend on it and how to confirm they still work.
Apache 2.4.67 brought that maintenance problem into focus. For business owners and agency teams, the useful response is a bounded review: establish patch status, identify the routes that matter, and give the upgrade an owner and a test plan.
What changed—and which release matters now?
Apache 2.4.67 fixed CVE-2026-23918, an HTTP/2 double-free vulnerability with possible remote code execution affecting upstream 2.4.66. It also addressed issues involving AJP and delegated .htaccess configuration. Later releases fixed further vulnerabilities, so installing 2.4.67 is no longer a sufficient upstream target. See Apache’s security advisories for affected versions and conditions.
As of 31 October 2026, Apache lists 2.4.69, released on 1 October, as its latest stable release. For a distribution-managed installation, check the vendor’s supported package and security notices: its fixed package may retain an older upstream version number.
Start with business impact and actual exposure
Ask which customer journeys pass through the proxy before deciding the maintenance window. A working home page proves little about sign-in, payment callbacks or uploads. Record the public hostname, relevant path, backend destination and person who can validate each important journey.
| Finding | Priority | Next action |
|---|---|---|
| Public proxy with unknown patch status | Urgent verification | Match the installed package revision to vendor security notices. |
| HTTP/2 on an affected, unpatched build | Prioritise remediation | Confirm applicable advisories and arrange the supported update. |
| AJP, HTML rewriting or cookie rewriting in use | Review affected routes | Identify the backend, its trust boundary and required modules. |
ProxyRequests On |
Inspect immediately | Confirm forward proxying is intentional and restricted to authorised clients. |
| No route owner or recovery instructions | Resolve before deployment | Assign a validator and document how service will be restored. |
ProxyRequests deserves particular attention. It enables forward proxying; reverse proxying through ProxyPass works with it set to Off. Apache’s mod_proxy documentation explains the distinction. An enabled setting needs an access-control review, even when the customer-facing website appears normal.
Collect evidence before changing configuration
Have the administrator run these read-only checks with sufficient permissions. Depending on the distribution, the command may be apache2ctl rather than apachectl. Replace /etc/apache2 with the actual configuration directory, commonly /etc/httpd on Red Hat-family systems.
apachectl -v
apachectl -V
apachectl -M
apachectl -S
apachectl -t
grep -RniE 'Protocols|ProxyRequests|ProxyPass|RewriteRule|SetHandler|BalancerMember|AllowOverride|AllowOverrideList|ajp://' /etc/apache2These checks show the executable version, build settings, loaded modules, configured virtual hosts and syntax status. The search provides leads for tracing proxy routes and delegated configuration. Matches may be comments or inactive files; included configuration may live elsewhere. Follow the configuration used by the running service, including any custom startup arguments or container mounts.
Next, record the full installed package revision using the system’s package manager and compare it with the relevant vendor advisory. Canonical explains how backporting applies security fixes to maintained package versions. A version banner alone cannot establish whether those fixes are installed. Also confirm that the operating-system release and package repository still receive security updates.
Make the upgrade small enough to validate
Separate the immediate security update from a broader configuration redesign. Save the active configuration, package revisions and service startup details. Agree who performs the change, who tests the applications and what failure would trigger recovery. If several teams share the proxy, nominate one coordinator.
Rehearse in staging where possible. Apply the supported update, run apachectl -t, and restart through the distribution’s service manager as required to load the updated executable and modules. With multiple proxy nodes, drain and update them in sequence where the architecture permits. Confirm that the running service has picked up the update.
Validate real journeys against the pre-change baseline:
- Check redirects, canonical hostnames and expected access restrictions.
- Complete sign-in and sign-out, including redirects and session cookies.
- Test uploads, API requests and payment or integration callbacks where relevant.
- Exercise WebSockets and both HTTP/1.1 and HTTP/2 when offered.
- Check upstream TLS and, in a controlled environment, slow or unavailable backends.
During the agreed observation window, compare error rates, latency and resource use with the baseline. Investigate new authentication failures, redirect loops and 502, 503 or 504 responses. A syntax check confirms configuration parsing; application tests establish whether the service still does its job.
Leave a usable handover
After the update is stable, remove unused modules and routes through separate, tested changes. Review who can edit .htaccess. Where delegation remains necessary, AllowOverrideList can permit specific directives. Its permissions combine with AllowOverride, so adding a short list does not cancel broader permissions already granted.
The handover should contain a route map, named owners, patch evidence, test results, recovery instructions and the next review date. For an agency, this also makes the boundary between hosting, application support and client approval explicit.
If nobody can confidently explain the proxy between your customers and their applications, Greg can help scope the review and coordinate the upgrade, with clear responsibilities and a runbook your team can use afterward.
Related on GrN.dk
- Nginx 1.30 Changed Upstream Connections: What to Test Before You Upgrade
- Apache 2.4.68: Patch First, Then Audit Your Proxy Rules
- Apache 2.4.68: What to Check Before You Call It Patched
Need help with this kind of work?
Discuss your Apache proxy review with Greg Get in touch with Greg.