{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-68870 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-68870 is a medium-severity missing authorization vulnerability in Apache Airflow Microsoft Azure provider, published on 10 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-68870 and fix it if it is affected.\n\nWhat it is: CVE-2026-68870 is a medium-severity missing authorization vulnerability in Apache Airflow Microsoft Azure provider, published on 10 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-68870 in the wild and no public exploit code.\n\nAffected product: Apache Airflow Microsoft Azure provider. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-68870/ (Markdown: https://insights.sbomify.com/CVE-2026-68870/index.md)","id":"CVE-2026-68870","markdown":"https://insights.sbomify.com/CVE-2026-68870/index.md","name":"CVE-2026-68870","record":{"aliases":["CLEANSTART-2026-KZ27328","GHSA-6hj8-q7v2-996c"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Airflow Azure provider","requires_auth":"low_privilege","summary":"Attackers in multi-team Airflow deployments can bypass team-scope guards to read secrets belonging to other teams via the Azure Key Vault backend.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"The Azure Key Vault secrets backend in Apache Airflow's Microsoft Azure 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-microsoft-azure 14.1.0 or later, which refuses the team-agnostic fall-through for an id that could name a team namespace.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Missing authorization in Apache Airflow Microsoft Azure provider","id":"CVE-2026-68870","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Apache Airflow Yandex Lockbox backend allows cross-team secret disclosure","id":"CVE-2026-68871"},"packages":[],"prev":{"headline":"This CVE ID was assigned in error.","id":"CVE-2026-68869"},"products":["Apache Airflow Microsoft Azure provider"],"published":"2026-08-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-16","vendors":["Apache Software Foundation"]},"summary":"Attackers in multi-team Airflow deployments can bypass team-scope guards to read secrets belonging to other teams via the Azure Key Vault backend.","url":"https://insights.sbomify.com/CVE-2026-68870/"}