# Apache Airflow secrets in rendered templates could contain parts of sensitive values when truncated

Advisory record · `GHSA-3qmm-r55x-hpxx`

- **Identifiers:** `GHSA-3qmm-r55x-hpxx` · `BIT-airflow-2025-68438` · `CVE-2025-68438` · `PYSEC-2026-9`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **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:** 16 Jan 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 16 Jan 2026, 12:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `apache-airflow` (PyPI): affected `>=3.1.0, <3.1.6`; fixed in `3.1.6`

## Machine-written summary

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

> Apache Airflow versions >=3.1.0 and <3.1.6 are affected. When rendered template fields exceed the max_templated_field_length setting, sensitive values can appear in cleartext in the Rendered Templates UI, because secrets registered with mask_secret() were not reliably masked before truncation. The source does not describe what level of access an attacker would need. Upgrade apache-airflow to 3.1.6 or later.

Written 1 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

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

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

## Timeline

- 16 Jan 2026, 10:06 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2025-68438)
- 16 Jan 2026, 11:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2025-68438)
- 31 Oct 2026, 14:11 UTC: First seen by agentprime
- 31 Oct 2026, 14:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-3qmm-r55x-hpxx)

## Sources

- [GitHub Advisory Database: GHSA-3qmm-r55x-hpxx](https://github.com/advisories/GHSA-3qmm-r55x-hpxx)
- [OSV: GHSA-3qmm-r55x-hpxx](https://osv.dev/vulnerability/GHSA-3qmm-r55x-hpxx)
- <https://nvd.nist.gov/vuln/detail/CVE-2025-68438>
- <https://github.com/apache/airflow>
- <https://github.com/pypa/advisory-database/tree/main/vulns/apache-airflow/PYSEC-2026-9.yaml>
- <https://lists.apache.org/thread/55n7b4nlsz3vo5n4h5lrj9bfsk8ctyff>
- <http://www.openwall.com/lists/oss-security/2026/01/15/5>

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-3qmm-r55x-hpxx>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-3qmm-r55x-hpxx/>. Everything for agents: <https://agentprime.io/llms.txt>.
