CVE-2026-129509

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-11-18. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory

Also known asEUVD-2026-128506 (ENISA EUVD) · GHSA-xf96-f68p-j448 (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan mitigationThe upstream fix is not in a release yet: until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high, then apply it (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.5Exploit: 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.

In the Apache Airflow Microsoft Azure provider 10.2.0 through 15.3.0, S3ToAzureBlobStorageOperator turned off TLS certificate verification for its connection to Amazon S3 by default (s3_verify=False), whatever the AWS connection's own verification settings were. An attacker positioned on the network between an Airflow worker and S3 could intercept that traffic, read the signed requests and alter the listed object keys and the copied file contents. Deployments are affected when a Dag uses S3ToAzureBlobStorageOperator without setting s3_verify. Users are advised to upgrade to apache-airflow-providers-microsoft-azure 15.3.1 or later, which uses the AWS connection's verification settings by default.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: An upstream fix is merged but not yet in a tagged release. Until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high, then apply it.
EPSS PROB
0.3%
EPSS %ILE
20th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

An upstream fix is merged but not yet in a tagged release. Until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high, then apply it.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 18, 2026

Last Modified

November 20, 2026

Advisory Details (3)

Auto-updated Nov 19, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
Web page

oss-security - CVE-2026-129509: Apache Airflow Microsoft Azure provider: S3ToAzureBlobStorageOperator disables S3 TLS verification by default

http://www.openwall.com/lists/oss-security/2026/11/17/30
GitHub pull request

Verify S3 TLS certificates by default in S3ToAzureBlobStorageOperator

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

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

Vendor Advisories for CVE-2026-129509(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 11× in last 7d / 11× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  2. 2026-11-20 17:49 UTCEchelonGraph re-scored
  3. 2026-11-20 17:49 UTCGHSA enrichmentGHSA-xf96-f68p-j448 · GitHub severity HIGH · GitHub CVSS 7.5
  4. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  5. 2026-11-19 20:29 UTCGHSA enrichmentGHSA-xf96-f68p-j448
  6. 2026-11-19 20:26 UTCOSV refresh
  7. 2026-11-19 20:04 UTCEchelonGraph re-scoredFirst assessed: 7.5 HIGH
  8. 2026-11-19 20:04 UTCGHSA enrichmentGHSA-xf96-f68p-j448
  9. 2026-11-19 20:03 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  10. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-11-18 12:50 UTCGHSA enrichmentGHSA-xf96-f68p-j448
  12. 2026-11-18 10:03 UTCENISA EUVD ID recordedEUVD-2026-128506 · Source: ENISA EUVD
  13. 2026-11-18 09:43 UTCEchelonGraph re-scored
  14. 2026-11-18 09:42 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-129509?
CVE-2026-129509 is a high-severity vulnerability; its CVE record was published on November 18, 2026. In the Apache Airflow Microsoft Azure provider 10.2.0 through 15.3.0, S3ToAzureBlobStorageOperator turned off TLS certificate verification for its connection to Amazon S3 by default (s3_verify=False), whatever the AWS connection's own verification settings were. An attacker positioned on the…
When was the CVE record for CVE-2026-129509 published?
The CVE record for CVE-2026-129509 was published on November 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 20, 2026; the record at its source may have been updated since.
Is CVE-2026-129509 actively exploited?
CVE-2026-129509 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-129509?
CVE-2026-129509 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-129509?
An upstream fix for CVE-2026-129509 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-129509 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-129509?

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