← Back
CVE-2026-24905
Command Injection in github.com/inspektor-gadget/inspektor-gadget (CVE-2026-24905)
Summary
command injection in github.com/inspektor-gadget/inspektor-gadget (CVE-2026-24905). Risk of unauthorized operations or information disclosure. Exploitable via ``Makefile.build``. Mitigation: upgrade to `0.51.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-24905** has been found in github.com/inspektor-gadget/inspektor-gadget.
Attackers can target a specific entry point like ``Makefile.build`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade github.com/inspektor-gadget/inspektor-gadget to **0.51.1** or later.
If unsure, ask your IT team or search "github.com/inspektor-gadget/inspektor-gadget CVE-2026-24905" on the vendor's site.
CVE-2026-24905 (github.com/inspektor-gadget/inspektor-gadget) — CWE-77 /
Attack surface: `Makefile.build` / `buildOptions` / `build.yaml` / `gadget.yaml`
Patched: `0.51.1` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-77) exists in github.com/inspektor-gadget/inspektor-gadget. Attackers reach the vulnerable code path via ``Makefile.build`` without authentication.
📍 Affected scope
github.com/inspektor-gadget/inspektor-gadget — . Attack surface: `Makefile.build` / `buildOptions` / `build.yaml` / `gadget.yaml`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.51.1**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'github.com/inspektor-gadget/inspektor-gadget' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/inspektor-gadget/inspektor-gadget' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/inspektor-gadget/inspektor-gadget` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/inspektor-gadget/inspektor-gadget to 0.51.1ステージング環境で 0.51.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Go
github.com/inspektor-gadget/inspektor-gadget
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.51.1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-24905
- package https://github.com/inspektor-gadget/inspektor-gadget
- web https://github.com/inspektor-gadget/inspektor-gadget/security/advisories/GHSA-79qw-g77v-2vfh
- web https://github.com/inspektor-gadget/inspektor-gadget/commit/7c83ad84ff7a68565655253e2cf1c5d2da695c1a
- web https://github.com/inspektor-gadget/inspektor-gadget/commit/d9bf2fe4a180dad33ce57ca793ff4799ee7b8320