Skip to main content
VulnerabilityPublished

CVE-2026-18980: nearai ironclaw · Injection

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-18980· Medium 5.3

Public exploit available · CVSS 5.3 Medium.

Data as of 5 Nov 2026, 23:24 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.6% chance of exploitation in 30 days – higher than 76% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
nearaiironclawAffected
  • =0.29.0
  • =0.29.1
Fixed in–
crates.iogithub/nearai/ironclawpkg:cargo/github/nearai/ironclawOther threatsAffected
  • =0.29.0
  • =0.29.1
Fixed in–

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

AI-suggested

Apply the patch identified by commit a1d7c3ba428ed575900469b207fb5668725f9a71 to resolve the vulnerability. No other mitigation or workaround is indicated. Prompt patching is advised to prevent exploitation.

Description

A command injection vulnerability exists in nearai ironclaw up to version 0.29.1 in the function classify_command_risk within src/tools/builtin/shell.rs. This vulnerability allows remote attackers with low privileges to execute arbitrary commands. Public exploit code is available. A patch identified by commit a1d7c3ba428ed575900469b207fb5668725f9a71 has been released to address this issue.

References

Community reviews

Loading reviews…