CVE-2017-17836 json
Apache Airflow vulnerable to XSS
published 2019-01-23 7 y ago modified 2026-06-17 4 mo ago also GHSA-9gqg-3fxr-9hv7 , PYSEC-2019-149 , EUVD-2019-0014
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.2%
- EPSS 3.2% chance of exploitation in 30 days, percentile 88%
- public exploits
- 0
- none known
Summary
In Apache Airflow 1.8.2 and earlier, an experimental Airflow feature displayed authenticated cookies, as well as passwords to databases used by Airflow. An attacker who has limited access to airflow, whether it be via XSS or by leaving a machine unlocked can exfiltrate all credentials from the system.
Patch / fix
- pypi apache-airflow 1.9.0
Exploit prediction
3.19% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
| GitHub | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | apache-airflow | <1.9.0 |
1.9.0 |
Affected products
- Apache Software Foundation Apache Airflow
Classification
References
- lists.apache.org /thread.html/ade4d54ebf614f68dc81a08891755e60ea58ba88e0209233eeea5f57%40%3Cdev.airflow.apache.org%3E
-
nvd.nist.gov
/vuln/detail/CVE-2017-17836
advisory
-
github.com
/advisories/GHSA-9gqg-3fxr-9hv7
advisory
-
github.com
/apache/airflow
package
-
github.com
/pypa/advisory-database/tree/main/vulns/apache-airflow/PYSEC-2019-149.yaml
web
-
lists.apache.org
/thread.html/ade4d54ebf614f68dc81a08891755e60ea58ba88e0209233eeea5f57@%3Cdev.airflow.apache.org%3E
web
Sources
- CVE List CVE-2017-17836
- GitHub Advisory GHSA-9gqg-3fxr-9hv7
- NVD CVE-2017-17836
- OSV PYSEC-2019-149
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.