Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2026-25917 is a high-severity Deserialization of Untrusted Data (CWE-502) vulnerability in Apache Airflow. Its CVSS base score is 7.2 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 46% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-25917 is a deserialization vulnerability (CWE-502) in Apache Airflow prior to version 3.2.0, where Dag Authors—who are not intended to execute code in the webserver context—can craft malicious XCom payloads that trigger arbitrary code execution on the webserver. The issue stems from improper handling of these payloads, allowing trusted users to escalate their influence beyond expected boundaries. It carries a CVSS v3.1 base score of 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H), rated as High despite the vendor's assessment of Low severity due to the inherent trust in Dag Authors.
The vulnerability can be exploited by authenticated Dag Authors (requiring high privileges, PR:H), who have network access to the Airflow webserver. By crafting and pushing a specially designed XCom payload, an attacker achieves remote arbitrary code execution in the webserver's context, potentially compromising confidentiality, integrity, and availability with high impact (C:H/I:H/A:H) across the affected system.
Apache Airflow advisories recommend upgrading to version 3.2.0, which resolves the issue. Relevant discussions and patches are detailed in the GitHub pull request at https://github.com/apache/airflow/pull/61641, the Apache mailing list thread at https://lists.apache.org/thread/6whgpkqbh12rvpfmvcg8b0vwlv4hq3po, and the OSS-Security announcement at http://www.openwall.com/lists/oss-security/2026/04/17/9.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-23658
Vulnerability Data
Dag Authors, who normally should not be able to execute code in the webserver context could craft XCom payload causing the webserver to execute arbitrary code. Since Dag Authors are already highly trusted, severity of this issue is Low. Users…
more
are recommended to upgrade to Apache Airflow 3.2.0, which fixes the issue.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can uncover deserialization flaws before deployment.
Input validation directly stops deserialization of untrusted data by ensuring inputs are valid before processing.
Engineering principles such as safe deserialization and input sanitization structurally prevent the weakness from being introduced.
Integrity verification tools can detect malformed or tampered serialized data after the fact.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
PR.PS-02 addresses only post-deployment updates/patching and cannot prevent introduction of unsafe deserialization code, yet it can remediate some instances when the flaw exists in outdated libraries or components.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing includes validation of deserialization routines and the use of untrusted data, reducing the likelihood that unsafe object reconstruction will be deployed.
Requiring vetted libraries, regular updates and SAST before release reduces the likelihood that deserialization logic will accept and act on attacker-controlled serialized objects.
Regular scanning of third-party libraries and timely patching reduce the likelihood that unsafe deserialization vulnerabilities remain active.
Mandatory malware scanning of data received over networks or storage media intercepts malicious serialized payloads before they are deserialized by the target application.