Skip to main content
VulnerabilityPublished Updated

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

Affects kimi-cliSource GCVE Database

0
Compare

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

Data as of 18 Nov 2026, 17:52 UTC

CVSS 4.0 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.84
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 kimi-cli to 0.84.

Affected software

ProductAffectedFixed in
Homebrewkimi-clipkg:brew/kimi-cliOther threatsAffected
  • >=0.76 <0.84
Fixed in
  • 0.84

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 kimi-cli to version 0.84 or later, where the vulnerability is fixed. Since a patch is available, applying this official fix is the recommended remediation. No alternative mitigations are specified.

Description

CVE-2025-27516 is a vulnerability in the Jinja sandbox environment used by kimi-cli versions 0.76 up to but not including 0.84. It allows an attacker who can control template content to execute arbitrary Python code by exploiting the interaction between the sandbox and the '|attr' filter, which bypasses sandbox restrictions on the 'format' method. The vulnerability is fixed in version 0.84.

References

Community reviews

Loading reviews…