Security readout for executives and security teams
Plain-English summary
Apache Airflow could expose workflow job logs without authentication when remote logging was not used. Those logs may contain operational details or secrets. Exposure depends on whether the built-in logging server was reachable from untrusted networks.
Executive priority
Treat this as a targeted information exposure risk, not confirmed widespread exploitation. Prioritize internet-facing or broadly reachable Airflow environments because exposed logs can leak credentials, business logic, and infrastructure details.
Technical view
In Apache Airflow before 2.1.2, CeleryExecutor workers or LocalExecutor schedulers could run a Flask logging server bound to 0.0.0.0 by default. The server lacked authentication and allowed reading DAG job log files, a CWE-200 information exposure issue.
Likely exposure
Most relevant to Apache Airflow deployments below 2.1.2 using CeleryExecutor or LocalExecutor without remote logging, especially where the logging server port is reachable beyond trusted hosts.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The risk is unauthenticated log access when the Airflow logging server is network-reachable.
Researcher notes
Evidence is limited to the CVE description and Apache reference. No CVSS score is provided in the bundle. Validate executor type, remote logging state, version, and network reachability before rating local severity.
Mitigation direction
- Upgrade Apache Airflow to 2.1.2 or later where feasible.
- Restrict access to Airflow logging server ports to trusted hosts only.
- Review Apache advisory guidance before changing executor or logging behavior.
- Audit DAG logs for exposed credentials or sensitive operational data.
Validation and detection
- Inventory Airflow versions and flag deployments below 2.1.2.
- Identify CeleryExecutor or LocalExecutor deployments without remote logging.
- Confirm whether logging server ports are reachable from untrusted networks.
- Review job logs for sensitive data that may require rotation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2021-35936 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://lists.apache.org/thread.html/r53d6bd7b0a66f92ddaf1313282f10fec802e71246606dd30c16536df%40%3Cusers.airflow.apache.org%3ECVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.