Skip to main content
Vulnerability Database/CVE-2026-47360

CVE-2026-47360: Apache HTTP Server Information Disclosure

CVE-2026-47360 is an information disclosure vulnerability in Apache HTTP Server's mod_session_cookie module that exposes session cookies to backend servers. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-47360 Overview

CVE-2026-47360 is an information disclosure vulnerability in the mod_session_cookie module of Apache HTTP Server. The flaw occurs when the SessionCookieRemove directive value changes across internal redirects. In this scenario, the session cookie that should have been stripped is still forwarded to the backend server. A remote attacker reaching a vulnerable reverse proxy configuration can observe or trigger conditions where sensitive session identifiers leak to unintended backends. The issue is tracked under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor and affects Apache HTTP Server versions 2.4.0 through 2.4.68.

Critical Impact

Session cookies managed by mod_session_cookie may be transmitted to backend servers that should never receive them, exposing authenticated session material to unauthorized components.

Affected Products

  • Apache HTTP Server 2.4.0 through 2.4.68
  • Deployments using the mod_session_cookie module
  • Reverse proxy configurations that alter SessionCookieRemove across internal redirects

Discovery Timeline

  • 2026-10-01 - CVE-2026-47360 published to NVD
  • 2026-10-02 - Last updated in NVD database

Technical Details for CVE-2026-47360

Vulnerability Analysis

Apache HTTP Server's mod_session_cookie module stores session state inside an HTTP cookie exchanged with the client. The SessionCookieRemove directive instructs the server to strip the session cookie from the request before it is forwarded to a backend application, preventing the backend from reading raw session material. The vulnerability occurs when the active value of SessionCookieRemove differs between the initial request context and an internal redirect target. The module does not re-evaluate the removal state after the internal redirect, so the session cookie survives into the proxied request. Backend applications, upstream services, or log sinks that record forwarded headers may then capture authenticated session tokens.

Root Cause

The root cause is incomplete state propagation across Apache internal redirects. mod_session_cookie reads the removal directive during the initial request phase and does not re-check it after the request context changes through subrequests or redirects handled by directives such as mod_rewrite or ErrorDocument. This produces an inconsistent policy where configuration intent and runtime behavior diverge.

Attack Vector

Exploitation requires a vulnerable Apache configuration that both uses mod_session_cookie and changes SessionCookieRemove across internal redirects. An unauthenticated remote attacker triggers a request path that invokes the internal redirect. The forwarded cookie reaches the backend, where it may be logged, reflected, or processed outside the trust boundary. No user interaction or privileges are required. The vulnerability affects confidentiality of session identifiers but does not directly modify data or disrupt availability. See the Apache HTTP Server Vulnerabilities page and the Openwall OSS Security announcement for upstream details.

Detection Methods for CVE-2026-47360

Indicators of Compromise

  • Backend application logs containing raw Cookie: headers with session identifiers that should have been stripped by mod_session_cookie.
  • Unexpected session cookie values appearing in upstream request traces after an internal redirect, ErrorDocument, or mod_rewrite rule fires.
  • Backend access logs that correlate forwarded session tokens with URIs configured for SessionCookieRemove On.

Detection Strategies

  • Audit Apache configurations for mod_session_cookie usage combined with any directive that changes SessionCookieRemove scope, including <Location>, <Directory>, <If>, and .htaccess overrides.
  • Replay representative request flows through staging and inspect proxied requests on the backend using tcpdump, mod_dumpio, or a reverse proxy capture to confirm cookie stripping behavior.
  • Compare the SessionCookieRemove state resolved for the initial request versus the final internal redirect target.

Monitoring Recommendations

  • Alert when backend logs contain cookie names matching the SessionCookieName configured on the front-end Apache instance.
  • Monitor Apache versions reported by httpd -v across the fleet and flag any instance at or below 2.4.68.
  • Track configuration drift on web tier hosts that introduces new SessionCookieRemove overrides inside internal redirect paths.

How to Mitigate CVE-2026-47360

Immediate Actions Required

  • Inventory all Apache HTTP Server instances between 2.4.0 and 2.4.68 and prioritize those using mod_session_cookie.
  • Upgrade affected servers to the fixed Apache HTTP Server release listed on the Apache HTTP Server Vulnerabilities page.
  • Rotate session secrets and invalidate active sessions if backend logs show forwarded session cookies that should have been stripped.

Patch Information

The Apache HTTP Server project addresses CVE-2026-47360 in a release later than 2.4.68. Review the Apache HTTP Server 2.4 vulnerabilities advisory for the exact fixed version and apply the vendor-supplied package for your distribution. Rebuild any custom Apache binaries against the patched source tree before redeployment.

Workarounds

  • Apply a uniform SessionCookieRemove policy at the outermost configuration scope so the directive does not change across internal redirects.
  • Terminate session cookie handling at a front proxy and forward only an opaque identifier to backends until patches are deployed.
  • Strip the session cookie explicitly before proxying using RequestHeader edit Cookie to remove the configured session cookie name.
bash
# Example front-end hardening until patched release is deployed
# Replace SESSION with the value of your SessionCookieName directive
RequestHeader edit Cookie "(^|; )SESSION=[^;]*;?" "" early
RequestHeader edit Cookie "^; " "" early
RequestHeader edit Cookie "; $" "" early

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.