VulnerabilityPublished 29 Sep 2026

CVE-2026-81862: Apache Airflow Teradata provider · Sensitive Data in Logs

Affects Apache Airflow Teradata providerSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 3.7.0 when convenient.

Data as of 13 Nov 2026, 23:54 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.7.0

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Apache Airflow Teradata provider and apache-airflow-providers-teradata to 3.7.0.

Affected software

Product	Affected	Fixed in
Apache Software FoundationApache Airflow Teradata provider	Affected <3.7.0	Fixed in 3.7.0
PyPIapache-airflow-providers-teradata`pkg:pypi/apache-airflow-providers-teradata`Other threats	Affected <3.7.0	Fixed in 3.7.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in apache-airflow-providers-teradata version 3.7.0 and later, which prevents credentials from appearing in Airflow task logs. Users should upgrade to this version to mitigate exposure in Airflow logs. However, credentials remain in Teradata's DBQL query logs and monitoring views, which Airflow cannot redact. To fully mitigate, users should configure the 'teradata_authorization_name' parameter with a Teradata AUTHORIZATION object to avoid inlining credentials in SQL statements. Additionally, any credentials previously exposed via logs should be rotated to prevent unauthorized access.

Description

Apache Airflow's Teradata provider versions before 3.7.0 embed cloud storage credentials directly into SQL statements, which are then logged in Airflow task logs and Teradata's query logs. This exposure occurs when using the S3ToTeradataOperator or AzureBlobStorageToTeradataOperator against private buckets without a configured Teradata authorization object. The credentials appear in plaintext in Airflow logs and Teradata's DBQL query logs, posing a risk of credential leakage. Upgrading to version 3.7.0 or later prevents credentials from appearing in Airflow logs but does not remove them from Teradata's logs. Users should configure a Teradata authorization object and rotate exposed credentials.

Impact

The vulnerability leads to exposure of sensitive cloud storage credentials in two logging systems: Airflow task logs and Teradata's DBQL query logs and monitoring views. This exposure allows any user with access to Airflow task logs or Teradata query logs to read plaintext credentials, potentially compromising cloud storage accounts. The impact is confidentiality loss of credentials, but no direct impact on integrity or availability is described. The CVSS score of 6.5 (medium severity) reflects network attack vector, low complexity, low privileges required, no user interaction, and high confidentiality impact.

Summary

The vulnerability CVE-2026-81862 in Apache Airflow's Teradata provider involves insertion of sensitive cloud storage credentials into SQL statements executed by the S3ToTeradataOperator and AzureBlobStorageToTeradataOperator. When these operators interact with private buckets and no Teradata authorization name is configured (the default), credentials are interpolated as plain string literals into the 'CREATE MULTISET TABLE ... LOCATION' SQL statement. This statement is logged in Airflow task logs (for S3ToTeradataOperator) and Teradata's DBQL query logs and live monitoring views (for both operators). The S3ToTeradataOperator exposes runtime AWS credentials including STS session tokens in Airflow logs, which are not masked. The AzureBlobStorageToTeradataOperator's credentials are masked in Airflow logs but still exposed in Teradata logs. The vulnerability affects versions >=0 and <3.7.0 of the apache-airflow-providers-teradata package. The issue is addressed in version 3.7.0 by preventing credentials from appearing in Airflow logs. However, credentials remain in Teradata logs unless a Teradata AUTHORIZATION object is configured to avoid inlining credentials. Credential rotation is recommended for any previously exposed credentials.

CWE-532Insertion of Sensitive Information into Log File (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A09:2025: Security Logging & Alerting Failures (opens in a new tab)
The product writes sensitive information to a log file.
Architecture and Design · Implementation
Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
Distribution
Remove debug log files before deploying the application into production.
Operation
Protect log files against unauthorized read/write.
OWASP Cheat Sheets
Application Logging Vocabulary (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V7.1.1 (opens in a new tab)
V7.1.2 (opens in a new tab)
V8.3.5 (opens in a new tab)
Attack patterns
Fuzzing for application mapping (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Oct 2026, 21:26 UTC

WeaknessesCWE-532

Technical details

References

Community reviews

Related threats