VYPR
← All advisories
Unrated severityNVD Advisory· Published Jun 8, 2026

CVE-2026-44119

CVE-2026-44119

Description

Apache HTTP Server 2.4.67 and earlier allows local .htaccess authors to read files with httpd user privileges.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Apache HTTP Server 2.4.67 and earlier allows local .htaccess authors to read files with httpd user privileges.

Vulnerability

An Improper Privilege Management vulnerability exists in Apache HTTP Server versions 2.4.0 through 2.4.67. This flaw allows a local attacker who can author .htaccess files to read arbitrary files on the server with the privileges of the httpd user [1].

Exploitation

An attacker must have the ability to create or modify .htaccess files within the web server's directory structure. By leveraging this write access, the attacker can then craft specific directives within these files to access and read files that would normally be restricted, effectively escalating their read privileges to match the httpd process user [1].

Impact

Successful exploitation allows an attacker to read arbitrary files on the server, including sensitive configuration files, source code, or other data accessible by the httpd user. This can lead to significant information disclosure and potential further compromise of the system [1].

Mitigation

Users are recommended to upgrade to Apache HTTP Server version 2.4.68, which was released on 2026-06-08 and fixes this issue. No workarounds are specified in the available references [1].

References
  1. Apache HTTP Server 2.4 vulnerabilities

AI Insight generated on Jun 8, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1

Patches

1
35c6e405390e

cookie reqest header counting (#324)

https://github.com/icing/mod_h2Stefan EissingMay 27, 2026via body-scan
commit
1 file changed · +4 −0
  • mod_http2/h2_util.c+4 −0 modified
    @@ -1708,6 +1708,8 @@ static apr_status_t req_add_header(apr_table_t *headers, apr_pool_t *pool,
              && !ap_cstr_casecmpn("cookie", (const char *)nv->name, nv->namelen)) {
         existing = apr_table_get(headers, "cookie");
         if (existing) {
+            if (!nv->valuelen)
+                return APR_SUCCESS;
             /* Cookie header come separately in HTTP/2, but need
              * to be merged by "; " (instead of default ", ")
              */
@@ -1719,6 +1721,8 @@ static apr_status_t req_add_header(apr_table_t *headers, apr_pool_t *pool,
             apr_table_setn(headers, "Cookie",
                            apr_psprintf(pool, "%s; %.*s", existing,
                                         (int)nv->valuelen, nv->value));
+            /* Treat the merge as an "add" to not escape LimitRequestFields */
+            *pwas_added = 1;
             return APR_SUCCESS;
         }
     }

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

1

News mentions

1