CVE REMEDIATION GUIDE
Review reviewCriticalFixed-version data available

CVE-2026-28780 remediation guide

Apache Software Foundation Apache HTTP Server, JBoss Core Services for RHEL 8, JBoss Core Services on RHEL 7

Heap-based Buffer Overflow vulnerability in mod_proxy_ajp of Apache HTTP Server. If mod_proxy_ajp connects to a malicious AJP server this AJP server can send a malicious AJP message back to mod_proxy_ajp and cause it to write 4 attacker controlled bytes after the end of a heap based buffer. This issue affects Apache HTTP Server: through 2.4.66. Users are recommended to upgrade to version 2.4.67, which fixes the issue.

Open CVE record
ProductApache Software Foundation Apache HTTP Server, JBoss Core Services for RHEL 8, JBoss Core Services on RHEL 7
Affected versions<= 2.4.66, < 2.4.67
Fixed versions2.4.67
Priority basisReview · CVSS 9.8 · EPSS 1.38%
01

Identify the affected asset

Confirm whether Apache Software Foundation Apache HTTP Server, JBoss Core Services for RHEL 8, JBoss Core Services on RHEL 7 is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: <= 2.4.66, < 2.4.67. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 2.4.67. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.