CVE-2026-86843

MEDIUMPre-NVD 6.36.3—
EchelonGraph scoreHIGH confidence

Score 6.3 from GitHub Security Advisory published 2026-09-29. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 6.3; sources differ by 0.0.

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

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

The Apache Airflow Teradata provider's compute-cluster example Dag declared every one of its Dag Params as unconstrained free text and templated them straight into the compute-cluster operators, which interpolate those values into Teradata DDL. A user who is permitted to trigger that Dag - a lower-trust role than the Dag author, and one that needs no Teradata credentials of its own - could therefore supply SQL fragments that execute under the connection the task runs as, and could additionally redirect the task at any other connection defined in the deployment, because the connection id was itself a free-text Param. Only deployments that run this example Dag, or a Dag copied from it, are affected; the provider's operator code is unchanged. Users of apache-airflow-providers-teradata are recommended to upgrade to version 3.7.0 or later, whose example constrains the Params to validated identifiers and a closed value set and removes connection selection and free-form option strings from trigger-time input. Upgrading does not change a Dag already copied from the example; users who copied it should apply the same constraints to their copy.

CVSS v3
6.3
EG Score
6.3MEDIUMhigh confidence
EG Risk
29
EG Risk 29/100CISA SSVC

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
Severity63% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
EPSS PROB
0.4%
EPSS %ILE
30th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 29, 2026

Last Modified

September 29, 2026

Advisory Details (2)

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

Constrain the Teradata compute-cluster example Dag's user-settable Params

Fix merged in apache/airflow PR #72714 on 2026-09-21 — awaiting tagged release

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

Vendor Advisories for CVE-2026-86843(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 21× 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-10-04 00:35 UTCEG score recompute
  2. 2026-10-04 00:35 UTCGHSA enrichment
  3. 2026-10-02 23:18 UTCEG score recompute
  4. 2026-10-02 23:18 UTCGHSA enrichment
  5. 2026-10-01 21:59 UTCEG score recompute
  6. 2026-10-01 21:59 UTCGHSA enrichment
  7. 2026-10-01 19:50 UTCEPSS rescore
  8. 2026-09-30 20:39 UTCEG score recompute
  9. 2026-09-30 20:39 UTCGHSA enrichment
  10. 2026-09-30 15:04 UTCEPSS rescore
  11. 2026-09-29 19:22 UTCGHSA enrichment
  12. 2026-09-29 18:50 UTCEG score recompute▲ 6.30
  13. 2026-09-29 18:49 UTCGHSA enrichment
  14. 2026-09-29 18:48 UTCMITRE cvelistV5CVSS v3 → 6.3 · severity → MEDIUM
  15. 2026-09-29 16:05 UTCGHSA enrichment
  16. 2026-09-29 12:33 UTCGHSA enrichment
  17. 2026-09-29 12:33 UTCNVD update
  18. 2026-09-29 11:23 UTCMITRE cvelistV5
  19. 2026-09-29 10:28 UTCNVD update
  20. 2026-09-29 10:20 UTCEG score recompute
  21. 2026-09-29 10:18 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-86843?
CVE-2026-86843 is a medium vulnerability published on September 29, 2026. The Apache Airflow Teradata provider's compute-cluster example Dag declared every one of its Dag Params as unconstrained free text and templated them straight into the compute-cluster operators, which interpolate those values into Teradata DDL. A user who is permitted to trigger that Dag - a…
When was CVE-2026-86843 disclosed?
CVE-2026-86843 was first published on September 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-86843 actively exploited?
CVE-2026-86843 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-86843?
CVE-2026-86843 has a CVSS v3.1 base score of 6.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-86843?
An upstream fix for CVE-2026-86843 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-86843 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-86843

Explore →

Is Your Infrastructure Affected by CVE-2026-86843?

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