Summary
Inspektor Gadget: Command Injection via malicious buildOptions manipulation
Impact
An attacker able to exploit this vulnerability would be able to execute arbitray command:
- on the Linux host where the
igcommand is launched, if images are built with the--localflag - on the build container invoked by
ig, if the--localflag is not provided
Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command. Typical impact: arbitrary command execution in the application's environment.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-24905? CVE-2026-24905 is a medium-severity command injection vulnerability in github.com/inspektor-gadget/inspektor-gadget (go), affecting versions < 0.51.1. It is fixed in 0.51.1. Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command.
- Which versions of github.com/inspektor-gadget/inspektor-gadget are affected by CVE-2026-24905? github.com/inspektor-gadget/inspektor-gadget (go) versions < 0.51.1 is affected.
- Is there a fix for CVE-2026-24905? Yes. CVE-2026-24905 is fixed in 0.51.1. Upgrade to this version or later.
- Is CVE-2026-24905 exploitable, and should I be worried? Whether CVE-2026-24905 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-24905 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-24905? Upgrade
github.com/inspektor-gadget/inspektor-gadgetto 0.51.1 or later.