Skip to content
Fencer Vulns
medium 4.3

CVE-2023-35798 json

Airflow Apache ODBC and MSSQL Providers Arbitrary File Read Vulnerability

published 2023-06-27 3 y ago modified 2026-07-13 3 mo ago also GHSA-q57w-826p-46jr , PYSEC-2026-1150 , PYSEC-2026-2370 , EUVD-2023-1863

cvss
4.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.3%
EPSS 1.3% chance of exploitation in 30 days, percentile 69%
public exploits
0
none known

Summary

Input Validation vulnerability in Apache Software Foundation Apache Airflow ODBC Provider, Apache Software Foundation Apache Airflow MSSQL Provider.This vulnerability is considered low since it requires DAG code to use `get_sqlalchemy_connection` and someone with access to connection resources specifically updating the connection to exploit it.

This issue affects Apache Airflow ODBC Provider: before 4.0.0; Apache Airflow MSSQL Provider: before 3.4.1.

It is recommended to upgrade to a version that is not affected

Patch / fix

  • pypi apache-airflow-providers-odbc 4.0.0
  • pypi apache-airflow-providers-microsoft-mssql 3.4.1
  • Apache Software Foundation Apache Airflow ODBC Provider 4.0.0
  • Apache Software Foundation Apache Airflow MSSQL Provider 3.4.1

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

1.26% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
GitHub 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
OSV 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
pypi apache-airflow-providers-odbc
<4.0.0
4.0.0
pypi apache-airflow-providers-microsoft-mssql
<3.4.1
3.4.1

Affected products

  • Apache Software Foundation Apache Airflow ODBC Provider
  • Apache Software Foundation Apache Airflow MSSQL Provider

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.