How to Fix CVE-2026-40690: CWE-1220: Insufficient Granularity of Access Control in Apache Airflow
By Sai Kiran Pandrala
Related fixes
Other vulnerabilities in the same area that are worth patching alongside this one:
- How to Fix CVE-2026-41636: Apache Thrift (Bundle Sibling) — Apache Thrift (Bundle Sibling)
- How to Fix CVE-2026-33227: Improper input validation for resource loading in Apache ActiveMQ Client — Improper input validation for resource loading in Apache ActiveMQ Client
- How to Fix CVE-2026-42812: Incorrect Authorization in Apache Polaris , Incorrect Authorization in Apache Polaris
- How to Fix CVE-2026-32690: Exposure of resource to wrong sphere in Apache Airflow , Exposure of resource to wrong sphere in Apache Airflow
- How to Fix CVE-2026-34476: Server-side request forgery in Apache SkyWalking MCP , Server-side request forgery in Apache SkyWalking MCP
Last verified: 2026-05-25
CVE-2026-40690 is a cwe-1220: insufficient granularity of access control in Apache Software Foundation Apache Airflow. Fix it by upgrading to the patched build from the vendor advisory.
| Severity | CVSS 4.3 - Medium |
|---|---|
| Actively exploited? | Not currently in the CISA KEV catalog |
| Affected | Apache Airflow 0 up to (excluding) 3.2.1 |
| Fixed in | See vendor advisory |
| Type (CWE) | CWE-1220: CWE-1220: Insufficient Granularity of Access Control |
What is CVE-2026-40690?
CVE-2026-40690 is a cwe-1220: insufficient granularity of access control flaw in Apache Software Foundation Apache Airflow. It carries a CVSS base score of 4.3 (medium). It is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
From the source record: The asset dependency graph did not restrict nodes by the viewer's DAG read permissions: a user with read access to at least one DAG could browse the asset graph for any other asset in the deployment and learn the existence and names of DAGs and assets outside their authorized scope.
Users are recommended to upgrade to version 3.2.1, which fixes this issue.
Why it matters in practice: The blast radius depends on how the affected service is exposed. An internet-facing instance with no compensating controls is the highest-risk configuration.
Am I affected?
You are affected if your installation of Apache Airflow matches a version listed in the Affected row above.
# Debian/Ubuntu
dpkg -s apache | grep Version
# RHEL/Rocky
rpm -q apache
How to fix CVE-2026-40690
Apply the vendor patch. Target the build named in the Fixed in row above (See vendor advisory). The runnable command set below covers the most common deployment patterns for Apache Airflow.
Ubuntu / Debian
sudo apt-get update
sudo apt-get install --only-upgrade apache
dpkg -s apache | grep Version
RHEL / CentOS / Rocky
sudo dnf upgrade apache -y
rpm -q apache
After applying the patch
- Restart the service or device so the patched binary loads.
- Confirm the running version matches the Fixed in row using the verification command below.
- Rotate credentials and API keys that the affected service could access if the asset was exposed during the disclosure window.
If you can't patch immediately
Until the patch lands, narrow the attack surface with these runnable controls.
Restrict network exposure
Block public access to the affected service at the perimeter. Allow only trusted source IPs.
# Linux iptables: only allow trusted admin subnet
sudo iptables -A INPUT -p tcp --dport 443 -s 10.10.10.0/24 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 443 -j DROP
sudo iptables-save | sudo tee /etc/iptables/rules.v4
# Windows firewall: only allow trusted admin subnet on management port
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Allow" -Direction Inbound -Action Allow `
-RemoteAddress 10.10.10.0/24 -Protocol TCP -LocalPort 443
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Deny" -Direction Inbound -Action Block `
-Protocol TCP -LocalPort 443
Mitigations are temporary. Apply the vendor patch as soon as a maintenance window opens.
How to verify the fix worked
Confirm the patched build is the one actually running.
# Debian/Ubuntu
dpkg -s apache | grep Version
# RHEL/Rocky
rpm -q apache
Expected: a version at or above the patched build named in the vendor advisory.
Also worth doing: pull recent log windows for indicators of compromise listed in the vendor advisory, and re-run an authenticated vulnerability scan with up-to-date signatures.
Frequently asked questions
Is CVE-2026-40690 being exploited in the wild?
As of 2026-05-25, CVE-2026-40690 is not listed in the CISA Known Exploited Vulnerabilities catalog. Watch the catalog and patch on a normal cadence; KEV status can change as exploitation evidence emerges.
What is the CVSS score for CVE-2026-40690?
The CVSS base score is 4.3 (Medium).
What version fixes this?
The vendor advisory names the patched build. See the References section.
Will a WAF or IDS rule alone close this?
No. Network filters cut down opportunistic scans but they do not remove the flaw. The vendor patch is the only durable fix.
References
- Official vendor advisory: https://lists.apache.org/thread/bqt7y4g2cpj396b0sd20lv510ff19ndl
- NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-40690
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Additional reference: https://github.com/apache/airflow/pull/65273
*Assembled from the official vendor advisory, the NVD record, and the CISA KEV listing on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*