VulnerabilityPublished 13 Aug 2026Updated 4 Nov 2026

CVE-2026-31236: llm CLI tool contains a code injection vulnerability via `--functions` command-line argument

Affects llmSource GCVE Database

Compare

Authoritative record:CVE-2026-31236· Critical 9.8

Not known to be exploited · CVSS 9.8 Critical : upgrade to 0.28 as a priority.

Data as of 4 Nov 2026, 20:35 UTC

CVSS 3.1 base score

9.8Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.28

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 4 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade llm to 0.28.

Affected software

Product	Affected	Fixed in
Homebrewllm`pkg:brew/llm`Other threats	Affected >=0.6 <0.28	Fixed in 0.28

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

AI-suggested

A patch is available in llm version 0.28 that fixes this vulnerability. Users should upgrade to version 0.28 or later to remediate the issue. Until upgraded, users should avoid running untrusted commands with the --functions argument and be cautious of social engineering attempts involving the llm CLI tool.

Description

The llm CLI tool up to version 0.27.1 has a critical code injection vulnerability in its --functions command-line argument. This argument allows users to input custom Python function definitions, but the tool unsafely executes this code using Python's exec() without any sanitization or restrictions. An attacker can exploit this by tricking a user into running a malicious command with arbitrary Python code, resulting in arbitrary code execution on the victim's system and potentially full system compromise. The vulnerability is fixed in version 0.28.

Impact

Exploitation of this vulnerability allows an attacker to execute arbitrary Python code on the victim's system with the privileges of the user running the llm tool. This can lead to full system compromise, including data theft, system manipulation, or further malware deployment. The vulnerability requires the victim to run a maliciously crafted command, typically via social engineering.

Summary

CVE-2026-31236 is a critical code injection vulnerability in the llm CLI tool versions >=0.6 and <0.28. The vulnerability arises because the --functions argument accepts user-supplied Python code and executes it directly with exec() without any security controls. This allows an attacker to execute arbitrary code on the victim's machine if the victim runs a crafted command. The flaw is due to the lack of input sanitization, sandboxing, or execution restrictions. The vulnerability has a CVSS 3.1 score of 9.8, indicating critical severity. A fix is available in llm version 0.28.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2026, 18:00 UTC

Technical details

References

Community reviews

Related threats