CVE-2025-69219: Apache Airflow Providers Http Unsafe Pickle Deserialization Leading to RCE

Summary

09/03/2026
Yes i
High
8.8

CVE-2025-69219: Apache Airflow Providers Http has Unsafe Pickle Deserializatio leading to RCE via HttpOperator. Affects apache-airflow-providers-http versions < 6.0.0. Fixed in 6.0.0. 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 Your last release was probably never penetration tested 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 Providers Http is a package that facilitates HTTP operations within Apache Airflow, a platform designed to programmatically author, schedule, and monitor workflows. This package allows users to execute HTTP requests as part of their workflows, enabling integration with various web services. However, the package has a critical vulnerability that exposes it to remote code execution (RCE) due to unsafe deserialization of pickle objects.

Vulnerability Detail

The vulnerability arises from the ability of a user with access to the database to craft a malicious database entry that, when triggered, executes arbitrary code on the Triggerer component of Apache Airflow. This effectively grants anyone with database access the same permissions as the DAG author, potentially leading to severe security breaches. Although direct database access is uncommon and not recommended for Airflow, the risk of exploitation remains significant, particularly in environments where database access controls are lax.

How To Fix

Latest published version: 6.3.0 as of 22 Oct 2026

pip install --upgrade "apache-airflow-providers-http==6.3.0"

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

If you need the minimum change

6.0.0

This is the first release that contains the fix.

pip install --upgrade "apache-airflow-providers-http==6.0.0"

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

Workaround

As a temporary measure, users can restrict direct database access and implement strict access controls to minimize the risk of exploitation until the package is updated. Additionally, consider using alternative methods for executing HTTP requests that do not involve the vulnerable components.

Conclusion

In summary, CVE-2025-69219 is a critical vulnerability in the Apache Airflow Providers Http package that allows for remote code execution through unsafe pickle deserialization. Users are strongly advised to upgrade to version 6.0.0 to secure their environments and mitigate potential risks.

See every vulnerability recorded for apache-airflow-providers-http →

Share this vulnerability

FAQ

The CVSS score of this vulnerability is 8.8, indicating a high severity level.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

If exploited, this vulnerability could allow an attacker to execute arbitrary code on the Triggerer, potentially compromising the entire Airflow environment.

Yes, the vulnerability requires direct access to the database, which is not typically recommended for Airflow deployments.

If an immediate upgrade is not possible, implement strict access controls and consider alternative methods for executing HTTP requests to mitigate the risk.

How To Fix

Latest published version: 6.3.0 as of 22 Oct 2026

pip install --upgrade "apache-airflow-providers-http==6.3.0"

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

If you need the minimum change

6.0.0

This is the first release that contains the fix.

pip install --upgrade "apache-airflow-providers-http==6.0.0"

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