dbcve.org
HTTP ServerWeb server / proxy · Apache

CVE-2026-34032

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-04
Fix available
A fix is available. Upgrade to 2.4.67 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Null Termination, Out-of-bounds Read vulnerability in Apache HTTP Server. This issue affects Apache HTTP Server: through 2.4.66. Users are recommended to upgrade to version 2.4.67, which fixes the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A vulnerability in Apache HTTP Server stemming from improper null termination allows an out-of-bounds read. This could potentially allow an attacker to access sensitive information by triggering the server to read beyond allocated buffer boundaries. The issue affects all versions through 2.4.66 and is resolved in version 2.4.67.

MitigationUpgrade Apache HTTP Server to version 2.4.67 or later to remediate this vulnerability. As this is a point release upgrade, organizations should follow standard change management procedures and verify compatibility with existing configurations after upgrading.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
HTTP ServerWeb server / proxy
Affected:< 2.4.67

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine Apache HTTP Server version
    Run 'httpd -v' or 'apache2 -v' or 'apachectl -v' to display the server version. On some systems, the binary may be located at /usr/sbin/httpd or /usr/sbin/apache2. Alternatively, check the package manager: 'rpm -q httpd' (RHEL/CentOS), 'dpkg -l apache2' (Debian/Ubuntu), or 'yum info httpd'.
    Affected if The installed version is any version prior to 2.4.67 (for example, 2.4.66, 2.4.55, 2.4.54, or earlier). The vulnerability affects all versions through 2.4.66.
  2. Verify Apache process is running
    Check if Apache is currently running as an active service. Use 'systemctl status httpd' or 'systemctl status apache2' on systemd-based systems, or 'service httpd status' on SysV init systems. You can also use 'ps aux | grep -E "httpd|apache2"' to list running Apache processes.
    Affected if Apache is actively running and the version is less than 2.4.67 (the server must be running for this vulnerability to be exploitable).
  3. Identify Apache binary location and version file
    Locate the Apache binary and any version information files. Common paths include /usr/sbin/httpd, /usr/sbin/apache2, /usr/local/apache2/bin/httpd. Also check for version files in /usr/local/apache2/build/ or within the installed package metadata.
    Affected if The binary or its version metadata shows a version number below 2.4.67.
  4. Review compiled server version at runtime
    If Apache is running, you can query it remotely or locally to confirm the exact version. Use 'curl -I http://localhost' or 'curl -I http://127.0.0.1' and inspect the Server header in the HTTP response. Some configurations may obscure the version; check httpd.conf for 'ServerTokens' and 'ServerSignature' directives.
    Affected if The Server header or internal version reporting reveals a version prior to 2.4.67.

A system is affected if Apache HTTP Server is installed and running with any version lower than 2.4.67, as the improper null termination vulnerability exists in all versions through 2.4.66.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.4.67 or later
Fixed in 2.4.67
Interim mitigation

Upgrade Apache HTTP Server to version 2.4.67 or later to remediate this vulnerability. As this is a point release upgrade, organizations should follow standard change management procedures and verify compatibility with existing configurations after upgrading.

Recommended fix High confidence

2.4.67

  1. Check current Apache HTTP Server version (e.g., httpd -v or apache2 -v)
  2. Backup current Apache configuration and document existing settings
  3. Upgrade Apache HTTP Server to version 2.4.67 using system package manager or compile from source
  4. Verify the upgrade was successful by checking the new version
  5. Restart Apache HTTP Server to load the fixed version
  6. Test that web services are functioning normally

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in HTTP Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34032 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34032 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data