Apache Vulnerability (CVE-2026-28779)
CVE-2026-28779
Apache Airflow versions 3.1.0 through 3.1.7 session token (_token) in cookies is set to path=/ regardless of the configured [webserver] base_url or [api] base_url. This allows any application co-hoste...
Overview
A security vulnerability, tracked as CVE-2026-28779, has been identified in Apache Airflow, a popular platform for programmatically authoring, scheduling, and monitoring workflows. This flaw affects session management and could allow an attacker to hijack a user’s active session.
Vulnerability Details
In affected versions (3.1.0 through 3.1.7), Airflow incorrectly sets the path for its session token cookie (_token). Regardless of the configured base_url for the webserver or API, the cookie is always set to path=/. This means the session token is sent in HTTP requests to any application or endpoint hosted on the same domain as the Airflow instance, not just to the Airflow application path.
Impact and Risk
The impact of this vulnerability is severe (CVSS score 7.5, HIGH). If another application is hosted under the same domain-for example, a different web app on the same server-that application can capture the valid Airflow session tokens from incoming HTTP request headers. An attacker controlling or compromising that co-hosted application could then use the stolen token to impersonate the user within Airflow without needing a password or directly attacking Airflow itself. This leads to a full session takeover, granting the attacker the same permissions and access as the compromised user, which could result in data theft, workflow manipulation, or further system compromise.
For context on the risks of credential exposure, recent incidents are detailed in our breach reports.
Remediation and Mitigation
The primary and most effective action is to upgrade Apache Airflow to version 3.1.8 or later. This update corrects the cookie path setting, ensuring session tokens are only sent to the intended Airflow base URL.
If an immediate upgrade is not possible, consider these temporary mitigation strategies:
- Isolate the Airflow Instance: Host Apache Airflow on its own dedicated domain or subdomain to prevent cookie sharing with other applications.
- Review Co-hosted Applications: Audit any other applications sharing the Airflow instance’s domain. Ensure they are fully trusted and secured, as they could become an attack vector.
- Monitor for Suspicious Activity: Increase monitoring of authentication logs and user sessions within Airflow for any unauthorized access.
Staying informed on such vulnerabilities is crucial for maintaining security posture. Follow the latest developments in our security news section.
Conclusion
CVE-2026-28779 is a high-risk session management flaw that undermines the isolation of the Apache Airflow application. Administrators should prioritize applying the official patch by upgrading to Airflow 3.1.8+ to prevent potential account takeover and protect their data orchestration environments.
Never miss a critical vulnerability
Get real-time security alerts delivered to your preferred platform.
Am I Affected by CVE-2026-28779?
Pick an ecosystem, paste your installed version, and we'll compare it against the fixed version published on OSV.dev. Browser-only — nothing is sent to a server.
Heuristic comparison only. Always cross-check against the vendor advisory before making patching decisions.
Related Advisories
Apache Airflow versions 3.1.0 through 3.1.7 missing authorization vulnerability in the Execution API's Human-in-the-Loop (HITL) endpoints that allows any authenticated task instance to read, approve, ...
Hashgraph Guardian through version 3.5.0 contains an unsandboxed JavaScript execution vulnerability in the Custom Logic policy block worker that allows authenticated Standard Registry users to execute...
A vulnerability in Cisco Smart Software Manager On-Prem (SSM On-Prem) could allow an unauthenticated, remote attacker to execute arbitrary commands on the underlying operating system of an affected SS...
Postiz is an AI social media scheduling tool. Prior to version 2.21.6, a file upload validation bypass allows any authenticated user to upload arbitrary HTML, SVG, or other executable file types to th...