Skip to content

docs(security): document supported deployment platforms#66931

Open
potiuk wants to merge 2 commits into
apache:mainfrom
potiuk:docs-security-supported-platforms
Open

docs(security): document supported deployment platforms#66931
potiuk wants to merge 2 commits into
apache:mainfrom
potiuk:docs-security-supported-platforms

Conversation

@potiuk
Copy link
Copy Markdown
Member

@potiuk potiuk commented May 14, 2026

Summary

Adds an explicit out-of-scope section for non-Linux platforms to the Security Model. Bugs that only manifest on Windows / macOS / other non-Linux platforms are not eligible for CVE allocation because Airflow does not officially support those platforms as deployment targets.

Motivation

Codifies what was already the security team's practice — most recently the disposition on a 2026-05-14 IMAP-attachment-path-traversal report (GHSA-w72r-xvc9-jwgh) that only manifested on Windows due to backslash path-separator handling, closed NOT-CVE-WORTHY on this basis.

Without an explicit Security Model section, reporters routinely submit Windows-only path-traversal / RCE reports that the team has to invalidate one-by-one with manual reasoning. Future Windows-only / macOS-only reports will be closed against this section, and reporters can read the rule upfront before submitting through security@.

The rule applies symmetrically: a bug that affects Linux is judged on the Linux behavior regardless of whether it also reaches Windows; non-Linux-only bugs are out of scope.

Test plan

  • Render the docs locally with breeze build-docs apache-airflow --package-filter apache-airflow and confirm the new section appears under the existing out-of-scope items in the Security Model page.
  • Spot-check that the new anchor #supported-deployment-platforms is generated correctly (Sphinx generates anchor IDs from heading text via kebab-case).

Add an explicit out-of-scope section for non-Linux platforms to the
Security Model. Bugs that only manifest on Windows / macOS / other
non-Linux platforms are not eligible for CVE allocation because Airflow
does not officially support those platforms as deployment targets.

Codifies what was already the security team's practice — most recently
the disposition on a 2026-05-14 IMAP-attachment-path-traversal report
that only manifested on Windows due to backslash path-separator
handling, closed NOT-CVE-WORTHY on this basis. Future Windows-only /
macOS-only reports get the same treatment, and reporters can read the
rule upfront before submitting.

The rule applies symmetrically: a bug that affects Linux is judged on
the Linux behavior regardless of whether it also reaches Windows;
non-Linux-only bugs are out of scope.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@potiuk potiuk added the backport-to-v3-2-test Mark PR with this label to backport to v3-2-test branch label May 14, 2026
@potiuk potiuk requested a review from amoghrajesh May 14, 2026 10:19
@potiuk potiuk added this to the Airflow 3.2.2 milestone May 14, 2026
@jscheffl
Copy link
Copy Markdown
Contributor

@potiuk I still have the aim and a task on my bucket list making Edge + Task SDK working on a Windows system. In Airflow 2.10 there was also a experimental setup documented in https://airflow.apache.org/docs/apache-airflow-providers-edge3/stable/install_on_windows.html - so I am not really good in excluding this.

Comment thread airflow-core/docs/security/security_model.rst Outdated
Comment thread airflow-core/docs/security/security_model.rst Outdated
Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-to-v3-2-test Mark PR with this label to backport to v3-2-test branch kind:documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants