PYSEC-2026-238

Vulnerability from pysec - Published: 2026-06-26 08:16 - Updated: 2026-06-27 10:28
VLAI
Details

The Apache Airflow FTP provider's FTPSHook.get_conn() created an ftplib.FTP_TLS connection but never called prot_p(), so although the control channel was TLS-protected the data channel was transmitted in cleartext. Any deployment using FTPSHook or FTPSFileTransmitOperator to move files over FTPS exposed file contents and credentials-in-transit to a network attacker able to observe the data connection. Upgrade apache-airflow-providers-ftp to 3.15.1 or later, which issues PROT P to encrypt the data channel.

Severity
7.5 (High)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Impacted products
Name purl
apache-airflow-providers-ftp pkg:pypi/apache-airflow-providers-ftp
Aliases
To clipboard 

{
  "affected": [
    {
      "ecosystem_specific": {},
      "package": {
        "ecosystem": "PyPI",
        "name": "apache-airflow-providers-ftp",
        "purl": "pkg:pypi/apache-airflow-providers-ftp"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "3.15.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "1.0.0",
        "1.0.0b1",
        "1.0.0b2",
        "1.0.0rc1",
        "1.0.1",
        "1.0.1rc1",
        "1.1.0",
        "1.1.0rc1",
        "2.0.0",
        "2.0.0rc1",
        "2.0.0rc2",
        "2.0.1",
        "2.0.1rc1",
        "2.1.0",
        "2.1.0rc1",
        "2.1.1",
        "2.1.1rc1",
        "2.1.2",
        "2.1.2rc1",
        "3.0.0",
        "3.0.0rc1",
        "3.0.0rc2",
        "3.1.0",
        "3.1.0rc1",
        "3.10.0",
        "3.10.0rc1",
        "3.10.1",
        "3.10.1rc1",
        "3.11.0",
        "3.11.0rc1",
        "3.11.1",
        "3.11.1rc1",
        "3.12.0",
        "3.12.0rc1",
        "3.12.0rc2",
        "3.12.1",
        "3.12.2",
        "3.12.2rc1",
        "3.12.3",
        "3.12.3rc1",
        "3.13.0",
        "3.13.0rc1",
        "3.13.1",
        "3.13.1rc1",
        "3.13.2",
        "3.13.2rc1",
        "3.13.3",
        "3.13.3rc1",
        "3.14.0",
        "3.14.0rc1",
        "3.14.1",
        "3.14.1rc1",
        "3.14.2",
        "3.14.2rc1",
        "3.14.3",
        "3.14.3rc1",
        "3.15.0",
        "3.15.0rc1",
        "3.15.1rc1",
        "3.2.0",
        "3.2.0rc1",
        "3.3.0",
        "3.3.0rc1",
        "3.3.0rc2",
        "3.3.1",
        "3.3.1rc1",
        "3.4.0",
        "3.4.0rc1",
        "3.4.0rc2",
        "3.4.1",
        "3.4.1rc1",
        "3.4.2",
        "3.4.2rc1",
        "3.5.0",
        "3.5.0rc1",
        "3.5.1",
        "3.5.1rc1",
        "3.5.2",
        "3.5.2rc1",
        "3.6.0",
        "3.6.0rc1",
        "3.6.1",
        "3.6.1rc1",
        "3.7.0",
        "3.7.0rc1",
        "3.8.0",
        "3.8.0rc1",
        "3.8.0rc2",
        "3.9.0",
        "3.9.0rc1",
        "3.9.1",
        "3.9.1rc1"
      ]
    }
  ],
  "aliases": [
    "CVE-2026-49486"
  ],
  "details": "The Apache Airflow FTP provider\u0027s `FTPSHook.get_conn()` created an `ftplib.FTP_TLS` connection but never called `prot_p()`, so although the control channel was TLS-protected the data channel was transmitted in cleartext. Any deployment using `FTPSHook` or `FTPSFileTransmitOperator` to move files over FTPS exposed file contents and credentials-in-transit to a network attacker able to observe the data connection. Upgrade apache-airflow-providers-ftp to `3.15.1` or later, which issues `PROT P` to encrypt the data channel.",
  "id": "PYSEC-2026-238",
  "modified": "2026-06-27T10:28:01.701706Z",
  "published": "2026-06-26T08:16:23.830Z",
  "references": [
    {
      "type": "WEB",
      "url": "http://www.openwall.com/lists/oss-security/2026/06/26/1"
    },
    {
      "type": "ADVISORY",
      "url": "https://lists.apache.org/thread/gwnsxlt9hfj5pc543wxtogbnjdn04xj1"
    },
    {
      "type": "FIX",
      "url": "https://github.com/apache/airflow/pull/67946"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
      "type": "CVSS_V3"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.