⚠️ 보안 공지: CVE-2025-66388, CVE-2025-65995(Apache Airflow3.1.0 ~ 3.1.3)

choo121600 · 12월 12, 2025, 9:51오전

Apache Airflow 3.1.x 버전에서 두 가지 보안 취약점이 발견되었습니다.
영향받는 버전은 Airflow 3.1.4 이전 모든 3.1.x 버전이며, 다행히 Airflow 3.1.4에서 모두 패치되었습니다.

운영 중인 환경에서 3.1.x를 사용하고 계시다면, 즉시 3.1.4 버전으로 업그레이드하시길 권장드립니다.

CVE-2025-65995: Disclosure of secrets to UI via kwargs

심각도: Moderate

문제 설명

Dag가 파싱 과정에서 실패할 경우, Airflow UI는 에러 내용을 보여주기 위해 traceback을 출력합니다.
이때 특정 Operator에 전달된 kwargs 전체가 그대로 포함되는 문제가 발견되었습니다.

만약 이 kwargs 안에 비밀번호, API Key, Token 등 민감한 값이 존재한다면,
해당 Dag를 볼 수 있는 모든 사용자에게 그대로 노출될 위험이 있습니다.

CVE-2025-66388: Secrets in rendered templates not redacted properly and exposed in the UI

심각도: Low

문제 설명

Airflow는 템플릿(Jinja) 렌더링 후 UI에서 값을 표시할 때,
민감한 값이 포함된 부분을 기본적으로 ***으로 마스킹하는 redaction 기능을 제공합니다.

하지만 특정 상황에서는 이 redaction 로직이 제대로 동작하지 않아,
렌더링된 템플릿 안에 비밀값이 그대로 노출될 수 있는 취약점이 확인되었습니다.

github.com/apache/airflow

Redact secrets in rendered templates properly to not expose them on UI

main ← astronomer:fix-mask-secret-rtif

열림 09:40AM - 27 Nov 25 UTC

amoghrajesh

+63 -1

### Problem Secrets registered via `mask_secret()` on the worker / dag processo…r (the ones those use task sdk secrets masker) are correctly masked in task logs but exposed in as clear text in the Rendered Templates UI. The root cause for this is that due to the recent move to move secrets masker to a shared library and using vendoring per distribution: https://github.com/apache/airflow/pull/54449, the task sdk uses a task sdk secrets masker is recognised differently from the core secrets masker by python even though they are logically the same. Python sees different import paths (`airflow.sdk.` vs `airflow.`and assumes that the maskers are different) The flow leading for logs vs rendered templates: 1. Task process calls `mask_secret()` -> sends `MaskSecret` message to supervisor 2. Supervisor registers the pattern in its `SecretsMasker` instance 3. **Logs:** Flow through supervisor's `SecretsMasker.filter()` an are masked 4. **Rendered templates:** Sent via `SetRenderedFields` message and supervisor forwards to API server which is stored in the database. 5. When UI tries to read it to display on the UI from the database, the masker that is used to redact it is the one in airflow core, hence the patterns registered with sdk masker are not recognised and masking fails. ### Solution Since the supervisor already has all secret patterns (from `MaskSecret` messages) but wasn't applying them to rendered template fields before sending to the API server, the solution is to redact at the worker end itself and send it across to the API server. This is the only way to do it and should not cause any ripple effects too because rendered templates are ONLY used to display to the user, and nothing else. ### Test #### Test 1: Running a Dag with custom operator with templated fields Dag: ```python from __future__ import annotations from datetime import datetime from airflow.decorators import dag from airflow.models import BaseOperator from airflow.sdk.log import mask_secret mask_secret("password") class CustomOperator(BaseOperator): template_fields = ("tup", "se") def __init__(self, tup: tuple, se: set, *args, **kwargs): super().__init__(*args, **kwargs) self.tup = tup self.se = se def execute(self, context): print(self.tup, self.se) @dag( catchup=False, tags=[], schedule=None, max_active_runs=1, start_date=datetime(2021, 1, 1), ) def hello_dag(): CustomOperator( task_id="custom", tup=(1, 2, "{{ds}}"), se={1, 2, 3, "password"}, ) hello_dag() ``` **Earlier:** Logs: <img width="2469" height="944" alt="image" src="https://github.com/user-attachments/assets/f853efb1-5085-4109-b7f1-393ce8faa0c5" /> Rendered fields: <img width="2469" height="944" alt="image" src="https://github.com/user-attachments/assets/de0de926-802b-4558-a8af-ebd79237871a" /> **After the fix:** Logs: <img width="2469" height="944" alt="image" src="https://github.com/user-attachments/assets/7c50cda7-1173-4493-8fe7-269bee323fff" /> Rendered Fields: <img width="2469" height="944" alt="image" src="https://github.com/user-attachments/assets/c892e2c4-ee37-4a79-95d1-648dd60f3e2b" /> #### Test 2: Using rendered templates with macros Plugin: ```python from airflow.plugins_manager import AirflowPlugin from airflow.models import Variable from airflow.sdk.log import mask_secret def get_masked_var(name: str): value = Variable.get(name) mask_secret(value) return value class TestPlugin(AirflowPlugin): name = "test_plugin" macros = [get_masked_var] ``` Set airflow variable using: ```shell script airflow variables set my_var "secret123" ``` DAG: ```python from airflow.sdk import DAG from airflow.providers.standard.operators.bash import BashOperator from datetime import datetime with DAG('macros_and_rtif', start_date=datetime(2024, 1, 1), schedule=None) as dag: BashOperator( task_id='test', bash_command='echo {{ macros.test_plugin.get_masked_var("my_var") }}' ) ``` **Before:** Logs: <img width="2469" height="944" alt="image" src="https://github.com/user-attachments/assets/f475a2a5-42a4-43bd-b8ee-3a08280b75eb" /> Rendered Templates: <img width="2469" height="944" alt="image" src="https://github.com/user-attachments/assets/8d5fce4c-6ca5-45fb-b304-d54dbd709c8c" /> **After:** Logs: <img width="2469" height="944" alt="image" src="https://github.com/user-attachments/assets/80e8e9d1-0333-4a77-8ff1-1e1cc7fec45a" /> Rendered Templates: <img width="2469" height="944" alt="image" src="https://github.com/user-attachments/assets/7fedcbb5-53a1-4e12-b557-23bd062c262b" /> --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)** for more information. In case of fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in a newsfragment file, named `{pr_number}.significant.rst` or `{issue_number}.significant.rst`, in [airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).

대응 방법

두 취약점은 모두 Airflow 3.1.4에서 완전히 수정되었습니다.
운영 중 Airflow 버전이 다음 중 하나라면:

3.1.0
3.1.1
3.1.2
3.1.3

즉시 3.1.4 버전으로 업그레이드를 권장합니다.
그럼 저도 업그레이드를… 하러

choo121600 · 12월 14, 2025, 4:02오전

3.1.4의 인증 부분 미들웨어에 버그가 있어서
3.1.5를 바로 릴리즈 했습니다. 3.1.5로 업그레이드하시길 권장드립니다..!