Cross-team secret disclosure via ambiguous Lockbox identifiers
Published Aug 10, 2026 · Updated Aug 10, 2026
Authorization bypass in Apache Airflow Yandex Provider before 4.5.1 allows remote authenticated users to read other teams' secrets. LockboxSecretBackend accepts a team-like Connection or Variable identifier, builds an ambiguous scoped name, and falls through to a team-agnostic lookup after a miss. The path requires multi-team mode and the Yandex Lockbox backend; access to one team suffices to obtain another team's stored credentials in full.
Summary
What happened
Authorization bypass in Apache Airflow Yandex Provider before 4.5.1 allows remote authenticated users to read other teams' secrets. LockboxSecretBackend accepts a team-like Connection or Variable identifier, builds an ambiguous scoped name, and falls through to a team-agnostic lookup after a miss. The path requires multi-team mode and the Yandex Lockbox backend; access to one team suffices to obtain another team's stored credentials in full.
The record
- CVE
- CVE-2026-68871
- Published
- Aug 10, 2026
- Updated
- Aug 10, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache Airflow Yandex Provider
- Classifications
- CWE-639, T1555.006
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 10, 2026CVE publishedPublication date reported by the CVE source.
- Aug 10, 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=0 <4.5.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Weakness, pattern, technique
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