# CVE-2023-46288: Apache Airflow: Sensitive parameters exposed in API when "non-sensitive-only" configuration is set > Authenticated users can read sensitive configuration data via the API when expose_config is set to non-sensitive-only, requiring an upgrade to fix. - **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 23 Oct 2023 - **Updated:** 13 Feb 2025 - **Also known as:** BIT-airflow-2023-46288, GHSA-9qqg-mh7c-chfq, PYSEC-2023-218 ## What is CVE-2023-46288? CVE-2023-46288 is a medium-severity vulnerability in Apache Airflow, published on 23 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Airflow.This issue affects Apache Airflow from 2.4.0 to 2.7.0. Sensitive configuration information has been exposed to authenticated users with the ability to read configuration via Airflow REST API for configuration even when the expose_config option is set to non-sensitive-only. The expose_config option is False by default. It is recommended to upgrade to a version that is not affected if you set expose_config to non-sensitive-only configuration. This is a different error than CVE-2023-45348 which allows authenticated user to retrieve individual configuration values in 2.7.* by specially crafting their request (solved in 2.7.2). Users are recommended to upgrade to version 2.7.2, which fixes the issue and additionally fixes CVE-2023-45348. Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2023-46288? 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 | From 2.4.0 | 2.7.0 | | `apache-airflow` | PyPI | From 2.4.0 | 2.7.2 | | `apache-airflow` | PyPI | From 2.4.0 | 2.7.2 | | `airflow` | Bitnami | From 2.4.0 | 2.7.0 | Products: Apache Airflow. ## How do I fix CVE-2023-46288? Upgrade apache-airflow to a fixed version for your release line: 2.7.0 or 2.7.2. ## Is CVE-2023-46288 being exploited? There is no known exploitation of CVE-2023-46288 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-2023-46288 and fix it if it is affected. What it is: CVE-2023-46288 is a medium-severity vulnerability in Apache Airflow, published on 23 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-46288 in the wild and no public exploit code. Affected packages and fixed versions: - apache-airflow (PyPI): affected from 2.4.0; fixed in 2.7.0 - apache-airflow (PyPI): affected from 2.4.0; fixed in 2.7.2 - apache-airflow (PyPI): affected from 2.4.0; fixed in 2.7.2 - airflow (Bitnami): affected from 2.4.0; fixed in 2.7.0 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-2023-46288/ (Markdown: https://insights.sbomify.com/CVE-2023-46288/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-46288 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-46288 - OSV: https://osv.dev/vulnerability/CVE-2023-46288 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-46288/ Summaries are generated and may contain mistakes; the official description above is the record.