CVE-2018-20244: Apache Airflow Arbitrary JavaScript Execution

apache-airflow Updated 02 Oct 2025

Summary

27/02/2019
Yes i
Moderate
5.5

CVE-2018-20244: In Apache Airflow before 1.10.2, a malicious admin user could edit the state of objects in the Airflow metadata database to execute arbitrary javascript on certain page views. Affects apache-airflow versions < 1.10.2. Fixed in 1.10.2. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Apache Airflow is an open-source platform used for programmatically authoring, scheduling, and monitoring workflows. It allows users to define complex workflows as Directed Acyclic Graphs (DAGs) and execute them on a variety of platforms. The vulnerability identified as CVE-2018-20244 allows a malicious admin user to manipulate the state of objects in the Airflow metadata database, leading to the execution of arbitrary JavaScript on certain page views.

Vulnerability Detail

The vulnerability arises from a lack of proper input validation and sanitization in Apache Airflow. By modifying the state of objects in the metadata database, an admin user can inject malicious JavaScript code that will be executed when certain pages are viewed. This can result in various consequences, including unauthorized access to sensitive information, cross-site scripting (XSS) attacks, and potential compromise of the Airflow platform.

How To Fix

Latest published version: 3.3.2 as of 22 Oct 2026

pip install --upgrade "apache-airflow==3.3.2"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.10.2

This is the first release that contains the fix.

pip install --upgrade "apache-airflow==1.10.2"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. However, as a general security practice, it is advisable to restrict admin privileges to trusted individuals and regularly monitor and audit the Airflow metadata database for any unauthorized changes.

Conclusion

The vulnerability identified as CVE-2018-20244 in Apache Airflow allows a malicious admin user to execute arbitrary JavaScript code by manipulating the state of objects in the metadata database. To mitigate this issue, it is crucial to upgrade to Apache Airflow version 1.10.2 or later. Regular monitoring and auditing of the metadata database are also recommended to detect any unauthorized changes. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for apache-airflow →

Share this vulnerability

FAQ

You can use the Vulert Playground at Vulert Scanner to check if your Apache Airflow installation is affected by this vulnerability. Simply provide the path to your Pipfile.lock, and Vulert will analyze it for any known vulnerabilities.

No, this vulnerability requires an admin user with access to the Airflow metadata database to exploit it. However, it is still crucial to address the issue promptly to prevent potential unauthorized access and further exploitation.

There have been no publicly reported instances of this vulnerability being exploited in the wild. However, it is always recommended to apply security patches and updates as soon as they become available to mitigate any potential risks.

No additional configuration is required after upgrading to Apache Airflow version 1.10.2 or later. The necessary fixes are included in the updated version, ensuring the mitigation of the vulnerability.

You can find more information about this vulnerability, including the technical details and the official advisory, in the Apache Airflow advisory database at https://github.com/pypa/advisory-database/blob/main/vulns/apache-airflow/PYSEC-2019-142.yaml.

Related vulnerabilities

Recent vulnerabilities recorded for apache-airflow.

How To Fix

Latest published version: 3.3.2 as of 22 Oct 2026

pip install --upgrade "apache-airflow==3.3.2"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.10.2

This is the first release that contains the fix.

pip install --upgrade "apache-airflow==1.10.2"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback