Cross-Dag log disclosure via lstrip character stripping
Published Jun 1, 2026 · Updated Jun 1, 2026
Incorrect authorization in Apache Airflow 3.0.0 through 3.2.1 allows remote authenticated users to read logs from other Dags. The log server applies Python str.lstrip() to the requested /log/ path before JWT-subject validation, removing a character set instead of the literal prefix. Exploitation requires a worker JWT for one Dag and exposes task output or error traces only when another Dag name begins with overlapping stripped characters.
Summary
What happened
Incorrect authorization in Apache Airflow 3.0.0 through 3.2.1 allows remote authenticated users to read logs from other Dags. The log server applies Python str.lstrip() to the requested /log/ path before JWT-subject validation, removing a character set instead of the literal prefix. Exploitation requires a worker JWT for one Dag and exposes task output or error traces only when another Dag name begins with overlapping stripped characters.
The record
- CVE
- CVE-2026-45426
- Published
- Jun 1, 2026
- Updated
- Jun 1, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache Airflow
- Classifications
- CWE-863, T1005
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 1, 2026CVE publishedPublication date reported by the CVE source.
- Jun 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.0.0 <3.2.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo