Cross-team credential disclosure via discarded team scope
Published Aug 12, 2026 · Updated Aug 12, 2026
Access-control bypass in Apache Airflow Google Provider before 22.3.0 allows remote authenticated users to read other teams' credentials. CloudSecretManagerBackend accepts team_name in get_conn_value and get_variable but omits it when calling _get_secret, which builds a team-agnostic secret name. Multi-team mode with the Google Secret Manager backend is required; a task or DAG in one team can obtain another team's Connection or Variable value in full.
Summary
What happened
Access-control bypass in Apache Airflow Google Provider before 22.3.0 allows remote authenticated users to read other teams' credentials. CloudSecretManagerBackend accepts team_name in get_conn_value and get_variable but omits it when calling _get_secret, which builds a team-agnostic secret name. Multi-team mode with the Google Secret Manager backend is required; a task or DAG in one team can obtain another team's Connection or Variable value in full.
The record
- CVE
- CVE-2026-68868
- Published
- Aug 12, 2026
- Updated
- Aug 12, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache Airflow Google Provider
- Classifications
- CWE-1220, T1555.006
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 12, 2026CVE publishedPublication date reported by the CVE source.
- Aug 12, 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 <22.3.0
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.
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