Skip to main content
VulnerabilityPublished Updated

CVE-2025-27516: Snowflake cli · Jinja2 vulnerable to sandbox breakout through attr filter selecting format method

Affects snowflake-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 5.4 Medium : upgrade to 3.5.0 when convenient.

Data as of 18 Nov 2026, 18:09 UTC

CVSS 4.0 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 3.5.0
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 17 Nov 2026.

What to do

Upgrade snowflake-cli to 3.5.0.

Affected software

ProductAffectedFixed in
Homebrewsnowflake-clipkg:brew/snowflake-cliOther threatsAffected
  • >=3.4.1 <3.5.0
Fixed in
  • 3.5.0

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

AI-suggested

Users should upgrade snowflake-cli to version 3.5.0 or later, where the vulnerability is fixed. Since a patch is available, applying this official fix fully mitigates the risk. No additional vendor advisory states otherwise.

Description

CVE-2025-27516 is a vulnerability in the snowflake-cli tool's use of the Jinja2 templating engine. It allows an attacker who can control template content to execute arbitrary Python code by exploiting a sandbox bypass via the |attr filter accessing the string format method. This affects versions from 3.4.1 up to but not including 3.5.0. The issue is fixed in version 3.5.0.

References

Community reviews

Loading reviews…