CVE-2026-81930

Apache Airflow's Snowflake provider did not validate the connection's `account` and `region` fields before interpolating them into request URLs. The SQL API endpoint is built as `https://{account}.snowflakecomputing.com/api/v2/statements`, so an `account` value containing `/`, `?` or `#` demotes the intended domain to a path, query or fragment and leaves the attacker in control of the request host. The provider sends that request with an `Authorization: Bearer` header carrying a JWT minted from the connection's private key, or the configured OAuth or programmatic access token. A user who can edit the Snowflake connection but cannot read its secrets — Airflow gives connection-configuration users write-only access to stored credentials, and a `private_key_file` lives on the worker rather than in the connection — can therefore cause a valid token for the account to be delivered to a host of their choosing and replay it against the genuine Snowflake endpoint. No Dag-authoring ability is required: the attacker edits the connection and waits for an existing Dag to use it. The same unvalidated value was also used to build the OAuth token-request URL and the Cortex Agent base URL. Affects deployments where Snowflake connections are editable by users who are not trusted with the connection's credentials. Users are advised to upgrade to `apache-airflow-providers-snowflake` `6.18.0` or later, which rejects `account` and `region` values containing anything other than letters, digits, `.`, `_` and `-` in every URL the provider builds from them.

• CWE-522

• https://github.com/apache/airflow/pull/72174Issue Tracking, Patch
• https://lists.apache.org/thread/324jm2mxd5x4nq85jfw1ostz94xwzrmkMailing List, Vendor Advisory
• https://www.openwall.com/lists/oss-security/2026/09/29/12Mailing List, Third Party Advisory

Published

Sep 29, 2026

Last Modified

Oct 7, 2026

Status

Analyzed

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-81925Concrete CMS before 9.5.3 improperly neutralized a user-supp…6.1
• CVE-2026-81926Concrete CMS 9.4.0 through 9.5.2 did not escape colliding pa…6.1
• CVE-2026-81927Concrete CMS before 9.5.3 contained a stored cross-site scri…5.4
• CVE-2026-81928Net::DNS versions before 1.57 for Perl allow memory exhausti…7.5
• CVE-2026-81929The Ocean Pro Demos and Ocean eComm Treasure Box plugins for…7.2
• CVE-2026-8193A weakness has been identified in Akaunting 3.1.21. This iss…6.3
• CVE-2026-81931Unrestricted Upload of File with Dangerous Type in the produ…4.8
• CVE-2026-81932IBM Guardium Data Protection 12.0, 12.1, and 12.2 is vulnera…9.8
• CVE-2026-81933IBM Guardium Data Protection 12.2 is vulnerable to a SQL inj…8.8
• CVE-2026-81934Redis contains a use-after-free vulnerability in the 'tlsPro…7.1
• CVE-2026-81936An internal security review identified a development regress…6.8
• CVE-2026-81937IBM Guardium Data Protection 12.2 is vulnerable to a command…7.2