PYSEC-2026-3715
Vulnerability from pysec - Published: 2026-08-10 19:17 - Updated: 2026-08-19 13:09The Yandex Lockbox secrets backend in Apache Airflow's Yandex provider resolved a team-scoped Connection or Variable id through the team-agnostic lookup when the team-scoped lookup missed. In a deployment running multi-team mode with this backend, a caller in one team could resolve a secret belonging to another team by supplying an id that spells out that team's namespace, obtaining its credentials in full. No unusual configuration is required beyond enabling multi-team mode and using this backend. Users are advised to upgrade to apache-airflow-providers-yandex 4.5.1 or later, which refuses the team-agnostic fall-through for an id that could name a team namespace.
| Name | purl | apache-airflow-providers-yandex | pkg:pypi/apache-airflow-providers-yandex |
|---|
{
"affected": [
{
"ecosystem_specific": {},
"package": {
"ecosystem": "PyPI",
"name": "apache-airflow-providers-yandex",
"purl": "pkg:pypi/apache-airflow-providers-yandex"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.5.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"1.0.0",
"1.0.0b1",
"1.0.0b2",
"1.0.0rc1",
"1.0.1",
"1.0.1rc1",
"2.0.0",
"2.0.0rc1",
"2.0.0rc2",
"2.1.0",
"2.1.0rc1",
"2.2.0",
"2.2.0rc1",
"2.2.1",
"2.2.1rc1",
"2.2.2",
"2.2.2rc1",
"2.2.3",
"2.2.3rc1",
"3.0.0",
"3.0.0rc1",
"3.0.0rc2",
"3.1.0",
"3.1.0rc1",
"3.1.0rc2",
"3.1.0rc3",
"3.10.0",
"3.10.0rc2",
"3.11.0",
"3.11.0rc1",
"3.11.1",
"3.11.1rc1",
"3.11.2",
"3.11.2rc1",
"3.12.0",
"3.12.0rc1",
"3.2.0",
"3.2.0rc1",
"3.2.0rc2",
"3.2.0rc3",
"3.3.0",
"3.3.0rc1",
"3.4.0",
"3.4.0rc1",
"3.5.0",
"3.5.0rc1",
"3.6.0",
"3.6.0rc1",
"3.7.0",
"3.7.0rc1",
"3.7.1",
"3.7.1rc1",
"3.8.0",
"3.8.0rc1",
"3.8.0rc2",
"3.9.0",
"3.9.0rc1",
"3.9.1rc1",
"4.0.0",
"4.0.0rc1",
"4.0.0rc2",
"4.0.1",
"4.0.1rc1",
"4.0.2",
"4.0.2rc1",
"4.0.3",
"4.0.3rc1",
"4.1.0",
"4.1.0rc1",
"4.1.1",
"4.1.1rc1",
"4.2.0",
"4.2.0rc1",
"4.2.1",
"4.2.1rc1",
"4.3.0",
"4.3.0rc1",
"4.3.1",
"4.3.1rc1",
"4.3.2",
"4.3.2rc1",
"4.3.3",
"4.3.3rc1",
"4.4.0",
"4.4.0rc1",
"4.4.1",
"4.4.1rc1",
"4.4.2",
"4.4.2rc1",
"4.5.0",
"4.5.0rc1",
"4.5.1rc1",
"4.5.1rc2"
]
}
],
"aliases": [
"CVE-2026-68871"
],
"details": "The Yandex Lockbox secrets backend in Apache Airflow\u0027s Yandex provider resolved a team-scoped Connection or Variable id through the team-agnostic lookup when the team-scoped lookup missed. In a deployment running multi-team mode with this backend, a caller in one team could resolve a secret belonging to another team by supplying an id that spells out that team\u0027s namespace, obtaining its credentials in full. No unusual configuration is required beyond enabling multi-team mode and using this backend. Users are advised to upgrade to apache-airflow-providers-yandex 4.5.1 or later, which refuses the team-agnostic fall-through for an id that could name a team namespace.",
"id": "PYSEC-2026-3715",
"modified": "2026-08-19T13:09:02.635411Z",
"published": "2026-08-10T19:17:30.463Z",
"references": [
{
"type": "ADVISORY",
"url": "http://www.openwall.com/lists/oss-security/2026/08/10/5"
},
{
"type": "ADVISORY",
"url": "https://lists.apache.org/thread/jlj9tv085txk4t0j029mvh43mz89o63c"
},
{
"type": "FIX",
"url": "https://github.com/apache/airflow/pull/70877"
}
],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.