# Apache Airlfow: Sensitive Azure Service Bus connection string (and possibly other providers) exposed to users with view access

Advisory record · `GHSA-4g48-54q2-fg7q`

- **Identifiers:** `GHSA-4g48-54q2-fg7q` · `BIT-airflow-2026-25219` · `CVE-2026-25219` · `PYSEC-2026-2344`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 15 Apr 2026
- **Updated:** 13 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 15 Apr 2026, 15:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `apache-airflow` (PyPI): affected `<3.1.8`; fixed in `3.1.8`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Apache Airflow versions before 3.1.8 do not mask the \`access_key\` and \`connection_string\` connection properties, so their values can be seen in the Connection UI by users with read permission and can appear in logs when a Connection is logged. Azure Service Bus stores sensitive values in these fields, and other providers may as well. Upgrade apache-airflow to 3.1.8 or later.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.0056, the 47th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 15 Apr 2026, 12:30 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-25219)
- 15 Apr 2026, 13:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-25219)
- 31 Oct 2026, 15:01 UTC: First seen by agentprime
- 31 Oct 2026, 15:01 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-4g48-54q2-fg7q)

## Sources

- [GitHub Advisory Database: GHSA-4g48-54q2-fg7q](https://github.com/advisories/GHSA-4g48-54q2-fg7q)
- [OSV: GHSA-4g48-54q2-fg7q](https://osv.dev/vulnerability/GHSA-4g48-54q2-fg7q)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-25219>
- <https://github.com/apache/airflow/pull/61580>
- <https://github.com/apache/airflow/pull/61582>
- <https://github.com/apache/airflow>
- <https://lists.apache.org/thread/t4dlmqkn0njz4chk3g7mdgzb96y4ttqh>
- <http://www.openwall.com/lists/oss-security/2026/04/15/3>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-4g48-54q2-fg7q>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-4g48-54q2-fg7q/>. Everything for agents: <https://agentprime.io/llms.txt>.
