Skip to content
VulniPulse
Medium6.5Apache Software Foundation

CVE-2026-81862: Apache Airflow's Teradata provider embedded cloud storage credentials directly into SQL statements

This Apache advisory covers CVE-2026-81862. Related products: Apache Airflow.

Open the Apache advisory

Key facts

Vendor rating
Medium, CVSS 6.5
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N · base score 6.5, scored by CISA-ADPAttack vector: network. Attack complexity: low. Privileges required: low. User interaction: none. Scope: unchanged. Confidentiality impact: high. Integrity impact: none. Availability impact: none.
Weakness
  • CWE-532: Insertion of Sensitive Information into Log File
EPSS
0.40% chance of exploitation in the next 30 days (35th percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: no. Technical impact: partial. CISA, .
CISA KEV
Not listed (catalogue checked )
Versions named
Apache Airflow Teradata provider before 3.7.0
Fixed in
3.7.0
Source published
Source revised
Listed by VulniPulse

Compiled by VulniPulse from the linked sources. How records are collected and checked.

Related products & platforms

Apache Software FoundationAirflow

Description

Apache Airflow's Teradata provider embedded cloud storage credentials directly into SQL statements. `S3ToTeradataOperator` and `AzureBlobStorageToTeradataOperator` interpolate the source bucket's credentials as plain string literals into the `CREATE MULTISET TABLE...

LOCATION` statement whenever the bucket is private and no `teradata_authorization_name` is configured — which is the default credential path for both operators. The statement is then logged and executed, so the credentials reach two places outside the operator's control.

The two operators expose different credentials through different channels, and deployments should check both.

`S3ToTeradataOperator` takes its values from `s3_hook.get_credentials()`, which under an instance profile or IRSA returns runtime AWS credentials that were never registered with Airflow's secrets masker — and the STS session token is runtime-generated and therefore unmasked even when an AWS connection is configured.

Those credentials appear **in the Airflow task log**, readable by any user with log-view permission on the Dag.

Text from the source record.

Versions named by the source
  • Apache Airflow Teradata provider before 3.7.0

Official advisory · high-confidence parse· fetched ·verify at source

How to fix CVE-2026-81862

Upgrade to the first fixed release for your version, shown in the table above.

Vendor guidance

  • Users are advised to upgrade to `apache-airflow-providers-teradata` `3.7.0` or later, which keeps the credential-bearing statement out of the Airflow task log.
  • Upgrading does not remove the credentials from Teradata's query logs and monitoring views, which Airflow cannot redact: users should configure `teradata_authorization_name` with a Teradata `AUTHORIZATION` object so that credentials are never inlined, and should rotate any credentials previously used through the inline path.

End-of-life dates for Apache Airflow

Apache Software Foundation advisories, September 2026All Apache Software Foundation advisories

Get an email when Apache Airflow publishes the next one.

See Apache Airflow's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Apache Airflow