Advisory record · GHSA-89cj-xrpx-j79m

A Dag author could either (a) create a symlink under their task's log directory pointing to an arbitrary file readable by the API server process (read-path attack — e.g. `/etc/passwd` or `airflow.c...

CVSS 6.5 MediumEPSS 0.0069 · 53rd 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-89cj-xrpx-j79m · BIT-airflow-2026-40861 · CVE-2026-40861 · PYSEC-2026-181
Weakness (CWE)
CWE-59
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) versions before 3.2.2 are vulnerable. A Dag author can create a symlink in their task's log directory pointing to a file the API server can read, or use a task_id with ".." sequences to write outside the configured log folder, leading to leaked or overwritten files. This affects only deployments where the worker and API server share a log folder. Upgrade to 3.2.2 or later; as a further mitigation, give the worker and API server separate log volumes.

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.0069, the 53rd percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 1 Jun 2026, 07:55 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.