CVE-2026-68076

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreHIGH confidence

Score 5.4 from GitHub Security Advisory published 2026-08-12. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.4
EG Score
5.4(high)
EG Risk
24(Track)
EG Risk 24/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity54% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

August 12, 2026

Last Modified

August 14, 2026

Advisory Details (3)

Auto-updated Aug 12, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
github_pr

Refuse a separator-bearing secret id before the team scoped lookup

Fix merged in apache/airflow PR #70902 on 2026-08-04 — awaiting tagged release

https://github.com/apache/airflow/pull/70902
github_pr

Only resolve a team namespaced environment secret for its own team

Fix merged in apache/airflow PR #70736 on 2026-08-01 — awaiting tagged release

https://github.com/apache/airflow/pull/70736

Vendor Advisories for CVE-2026-68076(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
apache-airflow1.10.0 ... 3.3.1rc2 (297 versions)3.3.1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 19× in last 7d / 33× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 02:56 UTCEG score recompute
  2. 2026-08-21 02:56 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 01:33 UTCEG score recompute
  5. 2026-08-20 01:33 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 00:10 UTCEG score recompute
  8. 2026-08-19 00:10 UTCGHSA enrichment
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-17 22:45 UTCEG score recompute
  11. 2026-08-17 22:45 UTCGHSA enrichment
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-16 21:22 UTCEG score recompute
  14. 2026-08-16 21:22 UTCGHSA enrichment
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-15 19:59 UTCEG score recompute
  17. 2026-08-15 19:59 UTCGHSA enrichment
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-14 18:35 UTCGHSA enrichment
  20. 2026-08-13 22:24 UTCEG score recompute
  21. 2026-08-13 22:24 UTCGHSA enrichment
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-12 21:01 UTCGHSA enrichment
  24. 2026-08-12 20:21 UTCGHSA enrichment
  25. 2026-08-12 19:21 UTCEG score recompute 5.40
Show 8 more
  1. 2026-08-12 19:21 UTCGHSA enrichment
  2. 2026-08-12 19:20 UTCMITRE cvelistV5CVSS v3 → 5.4 · severity → MEDIUM
  3. 2026-08-12 18:38 UTCGHSA enrichment
  4. 2026-08-12 18:37 UTCNVD update
  5. 2026-08-12 16:40 UTCMITRE cvelistV5
  6. 2026-08-12 16:33 UTCNVD update
  7. 2026-08-12 15:36 UTCEG score recompute
  8. 2026-08-12 15:35 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68076?
CVE-2026-68076 is a medium vulnerability published on August 12, 2026. 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…
When was CVE-2026-68076 disclosed?
CVE-2026-68076 was first published in the National Vulnerability Database on August 12, 2026, with the most recent update on August 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68076 actively exploited?
CVE-2026-68076 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 72.6% of all scored CVEs.
What is the CVSS score of CVE-2026-68076?
CVE-2026-68076 has a CVSS v3.1 base score of 5.4 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-68076?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68076, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-68076

Explore →

Is Your Infrastructure Affected by CVE-2026-68076?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.