# CVE-2021-26697: Apache Airflow: Lineage API endpoint for Experimental API missed authentication check

> Unauthenticated attackers can access lineage metadata for DAGs and tasks via the deprecated Experimental API endpoint in Apache Airflow.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Feb 2021
- **Updated:** 13 Feb 2025
- **Also known as:** BIT-airflow-2021-26697, GHSA-fh37-cx83-q542, PYSEC-2021-3

## What is CVE-2021-26697?

CVE-2021-26697 is a medium-severity missing authorization vulnerability in Apache Airflow, published on 17 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The lineage endpoint of the deprecated Experimental API was not protected by authentication in Airflow 2.0.0. This allowed unauthenticated users to hit that endpoint. This is low-severity issue as the attacker needs to be aware of certain parameters to pass to that endpoint and even after can just get some metadata about a DAG and a Task. This issue affects Apache Airflow 2.0.0.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2021-26697?

4 open source packages ship an affected version, including apache-airflow and airflow. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `apache-airflow` | PyPI | All versions | 2.0.1 |
| `apache-airflow` | PyPI | From 2.0.0 | 2.0.1rc1 |
| `apache-airflow` | PyPI | From 2.0.0 | 2.0.1rc1 |
| `airflow` | Bitnami | From 2.0.0 | 2.0.1 |

Products: Apache Airflow.

## How do I fix CVE-2021-26697?

Upgrade apache-airflow to a fixed version for your release line: 2.0.1 or 2.0.1rc1.

## Is CVE-2021-26697 being exploited?

There is no known exploitation of CVE-2021-26697 in the wild and no public exploit code.

## Other vulnerabilities in Apache Airflow

- [CVE-2020-13927](https://insights.sbomify.com/CVE-2020-13927/): Apache Airflow's Experimental API Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-11978](https://insights.sbomify.com/CVE-2020-11978/): Apache Airflow Command Injection (high 8.8, exploited in the wild)
- [CVE-2026-33264](https://insights.sbomify.com/CVE-2026-33264/): Apache Airflow: DAG author RCE on webserver via unrestricted import_string() in BaseSerialization.deserialize() (critical 9.8)
- [CVE-2023-25754](https://insights.sbomify.com/CVE-2023-25754/): Apache Airflow: Privilege escalation using airflow logs (critical 9.8)
- [CVE-2023-22884](https://insights.sbomify.com/CVE-2023-22884/): Apache Airflow, Apache Airflow MySQL Provider: Arbitrary file read via MySQL provider in Apache Airflow (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-26697 and fix it if it is affected.

What it is: CVE-2021-26697 is a medium-severity missing authorization vulnerability in Apache Airflow, published on 17 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-26697 in the wild and no public exploit code.

Affected packages and fixed versions:
- apache-airflow (PyPI): affected all versions; fixed in 2.0.1
- apache-airflow (PyPI): affected from 2.0.0; fixed in 2.0.1rc1
- apache-airflow (PyPI): affected from 2.0.0; fixed in 2.0.1rc1
- airflow (Bitnami): affected from 2.0.0; fixed in 2.0.1

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-26697/ (Markdown: https://insights.sbomify.com/CVE-2021-26697/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-26697
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-26697
- OSV: https://osv.dev/vulnerability/CVE-2021-26697

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-26697/
Summaries are generated and may contain mistakes; the official description above is the record.