Advisory record · GHSA-cg3x-89rc-x9mw

A bug in Apache Airflow's rendered-template field handling caused nested sensitive-key masking (e.g. nested `password` / `token` / `secret` / `api_key` keys inside a JSON template structure) to be ...

CVSS 6.5 MediumEPSS 0.0035 · 28th percentile

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

PackageEcosystemAffectedFixed in
apache-airflowPyPI<3.2.23.2.2
Identifiers
GHSA-cg3x-89rc-x9mw · BIT-airflow-2026-42360 · CVE-2026-42360 · PYSEC-2026-172
Weakness (CWE)
CWE-200
Published
1 Jun 2026
Updated
13 Jul 2026

Machine-written summary

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

Apache Airflow (apache-airflow, PyPI) versions before 3.2.2 are affected. When a rendered template field is longer than the core max_templated_field_length setting and contains nested sensitive keys such as password, token, secret, or api_key inside a JSON structure, Airflow stores the value in plaintext in rendered_fields instead of masking it. An authenticated user who can read rendered template fields through the UI or API could obtain those secrets. Upgrade to apache-airflow 3.2.2 or later.

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

ScoreRatingCVSSVectorSource
6.5 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N OSV
  • CISA KEV Not listed.
  • EPSS 0.0035, the 28th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 1 Jun 2026, 07:50 UTC Confirmed by the CVE List
  2. 1 Jun 2026, 09:16 UTC Confirmed by NVD
  3. 31 Oct 2026, 14:43 UTC First seen by agentprime
  4. 31 Oct 2026, 14:43 UTC Confirmed by OSV

Sources

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.