dbcve.org
HTTP ServerWeb server / proxy · Apache

CVE-2026-44119

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-08
Fix available
A fix is available. Upgrade to 2.4.68 or later.
See remediation →
57/100
Remediation priority · Elevated
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 Privilege Management vulnerability in Apache HTTP Server 2.4.67 and earlier allows local .htaccess authors to read files with the privileges of the httpd user. This issue affects Apache HTTP Server: from through 2.4.67. Users are recommended to upgrade to version 2.4.68, 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 · high confidence

Improper Privilege Management vulnerability in Apache HTTP Server 2.4.67 and earlier allows local .htaccess authors to read files with the privileges of the httpd user, enabling unauthorized file access beyond intended .htaccess scope.

MitigationUpgrade Apache HTTP Server to version 2.4.68 or later to remediate this vulnerability.

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.0, < 2.4.68

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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. Identify the installed Apache HTTP Server version
    Run 'httpd -v' or 'apache2 -v' (depending on OS) to retrieve the server version number
    Affected if The version shown is 2.4.0 or higher but lower than 2.4.68
  2. Verify if Apache httpd process is running
    Run 'ps aux | grep httpd' or 'systemctl status httpd' to confirm the Apache service is active
    Affected if Apache is running and the version from step 1 is vulnerable
  3. Confirm .htaccess file override capability is enabled
    Check the Apache configuration file (httpd.conf or apache2.conf) for 'AllowOverride' directives set to 'All' or 'FileInfo' in any directory block, or inspect the actual .htaccess file in a web directory
    Affected if AllowOverride is enabled (not set to 'None') and untrusted users can write to directories containing .htaccess files
  4. Assess write access to web-accessible directories
    Review file system permissions on web document root directories (commonly /var/www/html or /etc/httpd/conf.d) to determine if non-privileged or untrusted users have write permission to create or modify .htaccess files
    Affected if Untrusted users have write access to directories where .htaccess files can be placed

You are affected if Apache HTTP Server version is 2.4.0 through 2.4.67, the service is running, AllowOverride is not set to None, and untrusted users can create or modify .htaccess files in web-accessible directories.

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.68 or later
Fixed in 2.4.68
Interim mitigation

Upgrade Apache HTTP Server to version 2.4.68 or later to remediate this vulnerability.

Recommended fix High confidence

2.4.68

  1. 1. Back up the current Apache HTTP Server configuration and document your current version: cp -r /etc/apache2 /etc/apache2.bak (or cp -r /etc/httpd /etc/httpd.bak on RHEL-based systems)
  2. 2. Stop the Apache service: systemctl stop apache2 (or systemctl stop httpd on RHEL-based systems)
  3. 3. Update your package repository and upgrade Apache: apt-get update && apt-get install apache2 (Debian/Ubuntu) OR yum update httpd (RHEL/CentOS)
  4. 4. Verify the new version is 2.4.68: apache2 -v (or httpd -v on RHEL-based systems)
  5. 5. Review the new configuration for any deprecated directives in the release notes at httpd.apache.org
  6. 6. Start the Apache service: systemctl start apache2 (or systemctl start httpd on RHEL-based systems)
  7. 7. Test that the web server is functioning correctly and check the error log for any issues
Caveat Review the Apache 2.4.68 release notes for any configuration or module compatibility changes; upgrade is generally low-risk for minor version updates

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44119 — 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-44119 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