Skip to main content
VulnerabilityPublished Updated

CVE-2026-24905: inspektor-gadget · Command Injection

Affects inspektor-gadgetSource GCVE Database

0

Public exploit available · CVSS 6.6 Medium : upgrade to 0.51.1 as a priority.

Data as of 27 Oct 2026, 00:30 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Upgrade inspektor-gadget to 0.51.1.

Affected software

ProductAffectedFixed in
inspektor-gadget inspektor-gadgetAffected
  • <0.51.1
Fixed in
  • 0.51.1

AI-suggested

Upgrade Inspektor Gadget to version 0.51.1 or later, where this command injection vulnerability is fixed. Until then, avoid building images from untrusted gadget manifests or untrusted input to the `ig image build` command. No other mitigations are documented.

Description

Inspektor Gadget versions prior to 0.51.1 contain a command injection vulnerability in the image building subcommand of the `ig` binary. This flaw arises from unsafe inclusion of user-controlled data in Makefile commands during the build process. An attacker who can control the build options in the YAML gadget manifest used by `ig image build` may execute arbitrary commands on the Linux host or build container. This scenario is plausible in CI/CD pipelines that build untrusted gadgets. The issue is fixed in version 0.51.1.

References

Community reviews

Loading reviews…