Vulnerability in apache-airflow (CVE-2026-68076)
Summary
Vulnerability in apache-airflow (CVE-2026-68076). Risk of unauthorized operations or information disclosure. Exploitable via POST /api/v2/connections/test. Mitigation: upgrade to 3.3.1 or later.
Original description
The description as published by the source.
Apache Airflow's environment-variable secrets backend resolved a team-scoped Connection or Variable from the wrong team's scope. The guard meant to prevent this only ran when no team scope was supplied, and its pattern could not match a team name containing an underscore, which team names are allowed to contain. When the guard did not apply, the lookup fell through to an unconditional global read that resolved the stored AIRFLOW_CONN_____ variable regardless of which team asked. In multi-team mode an authenticated user of one team could therefore have POST /api/v2/connections/test resolve another team's Connection and authenticate outward with that team's credentials; the endpoint uses the credentials rather than returning them. Exploitation requires [core] multi_team enabled, [core] test_connection set to Enabled (it ships Disabled), team-scoped secrets provisioned as environment variables in the API-server process, and knowledge of the encoded identifier. Redirecting the test at an attacker-controlled host is separately blocked. Users are advised to upgrade to apache-airflow 3.3.1 or later.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-68076 has been found in apache-airflow.
Attackers can target a specific entry point like POST /api/v2/connections/test over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade apache-airflow to 3.3.1 or later.
If unsure, ask your IT team or search "apache-airflow CVE-2026-68076" on the vendor's site.
CVE-2026-68076 (apache-airflow) — CWE-639 / CVSS v3 5.4
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/v2/connections/test / Enabled / Disabled
Patched: 3.3.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-639) exists in apache-airflow. Attackers reach the vulnerable code path via POST /api/v2/connections/test.
Check the vendor advisory for the affected versions of apache-airflow. Attack surface: POST /api/v2/connections/test / Enabled / Disabled.
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.
Update to 3.3.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /api/v2/connections/test requests with malformed payloads or SQL meta-characters. Run grep -r 'apache-airflow' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'apache-airflow' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
apache-airflowを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /api/v2/connections/test' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/v2/connections/testへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade apache-airflow to 3.3.1ステージング環境で 3.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/v2/connections/test on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory lists.apache.org
- advisory nvd.nist.gov
- advisory openwall.com
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com