# CVE-2026-81862: Information disclosure in Apache Airflow Teradata provider > Attackers with log access can read cloud storage credentials exposed in Airflow task logs and Teradata query logs by the Teradata provider. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 29 Sep 2026 - **Updated:** 29 Sep 2026 - **Also known as:** GHSA-jcpw-3g4p-9hmj ## What is CVE-2026-81862? CVE-2026-81862 is a medium-severity vulnerability in Apache Airflow Teradata provider, published on 29 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official 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. `AzureBlobStorageToTeradataOperator` takes its storage account key from the connection, so the masker usually redacts the task-log copy; its exposure is the Teradata side. **Both** operators write the credentials into Teradata's DBQL query logs and live monitoring views, where Airflow's masking never applies and the values persist for that system's log retention period. Affects deployments using either operator against a private bucket or container without a Teradata `AUTHORIZATION` object. 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. Weakness: CWE-532 (Insertion of Sensitive Information into Log File) ## Which versions are affected by CVE-2026-81862? It affects 1 product. Products: Apache Apache-Airflow-Providers-Teradata. ## How do I fix CVE-2026-81862? No fix has been published for CVE-2026-81862 yet. Limit exposure of the affected software until one is available. ## Is CVE-2026-81862 being exploited? There is no known exploitation of CVE-2026-81862 in the wild and no public exploit code. ## Other vulnerabilities in Apache Airflow Teradata provider - [CVE-2026-86843](https://insights.sbomify.com/CVE-2026-86843/): Apache Airflow Teradata provider: SQL injection via unvalidated Dag Params in the compute-cluster example Dag (medium 6.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-81862 and fix it if it is affected. What it is: CVE-2026-81862 is a medium-severity vulnerability in Apache Airflow Teradata provider, published on 29 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-81862 in the wild and no public exploit code. Affected product: Apache Airflow Teradata provider. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-81862/ (Markdown: https://insights.sbomify.com/CVE-2026-81862/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-81862 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-81862 - OSV: https://osv.dev/vulnerability/CVE-2026-81862 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-81862/ Summaries are generated and may contain mistakes; the official description above is the record.