{"answers":{"affected":"1 open source package ship an affected version, including apache-airflow-providers-amazon. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-68872 in the wild and no public exploit code.","fix":"Upgrade apache-airflow-providers-amazon to 9.34.0 or later.","what":"CVE-2026-68872 is a medium-severity missing authorization vulnerability in Apache Airflow Amazon 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-68872 and fix it if it is affected.\n\nWhat it is: CVE-2026-68872 is a medium-severity missing authorization vulnerability in Apache Airflow Amazon 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-68872 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- apache-airflow-providers-amazon (PyPI): affected all versions; fixed in 9.34.0\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-68872/ (Markdown: https://insights.sbomify.com/CVE-2026-68872/index.md)","id":"CVE-2026-68872","markdown":"https://insights.sbomify.com/CVE-2026-68872/index.md","name":"CVE-2026-68872","record":{"aliases":["CLEANSTART-2026-VM33357","GHSA-984p-rgj2-h89x","PYSEC-2026-3713"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Apache Airflow Amazon provider","requires_auth":"low_privilege","summary":"Attackers in multi-team Airflow deployments can bypass team scoping to read secrets from other teams via AWS SSM or Secrets Manager backends.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"apache-airflow-providers-amazon","vendor":"apache"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/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 AWS Systems Manager Parameter Store and Secrets Manager backends in Apache Airflow's Amazon 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 either 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 one of these backends. Users are advised to upgrade to apache-airflow-providers-amazon 9.34.0 or later, which refuses the team-agnostic fall-through for an id that could name a team namespace.","ecosystems":["PyPI"],"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 Amazon provider","id":"CVE-2026-68872","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":1,"n_references":2,"next":{"headline":"Windows Program Compatibility Assistant Service Information Disclosure Vulnerability","id":"CVE-2026-68873"},"packages":[{"ecosystem":"PyPI","fixed":["9.34.0"],"introduced":["0"],"last_affected":[],"package":"apache-airflow-providers-amazon","purl":"pkg:pypi/apache-airflow-providers-amazon","source":"PYSEC-2026-3713"}],"prev":{"headline":"Apache Airflow Yandex Lockbox backend allows cross-team secret disclosure","id":"CVE-2026-68871"},"products":["Apache Airflow Amazon provider"],"published":"2026-08-10","related":[{"cvss_score":7.5,"headline":"Apache Airflow AWS Provider: Arbitrary file read via AWS provider","id":"CVE-2023-25956","kev_date_added":null,"published":"2023-02-24"},{"cvss_score":5.4,"headline":"Apache Airflow AWS Auth Manager - Host Header Injection Leading to SAML Authentication Bypass","id":"CVE-2026-25604","kev_date_added":null,"published":"2026-03-09"},{"cvss_score":5.3,"headline":"Apache Airflow Amazon provider: Prevent unauthorized access to team-scoped secrets in AWS Secrets Manager and SSM Parameter Store backends","id":"CVE-2026-42526","kev_date_added":null,"published":"2026-05-19"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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 scoping to read secrets from other teams via AWS SSM or Secrets Manager backends.","url":"https://insights.sbomify.com/CVE-2026-68872/"}