Summary
Inspektor Gadget Security Policies Can be Bypassed
Security policies like allowed-gadgets, disallow-pulling, verify-image can be bypassed by a malicious client.
The issue has been fixed in v0.40.0
Workarounds
There is not known workaround to fix it.
Impact
Users running ig in daemon mode or IG on Kubernetes that rely on any of the features mentioned above are vulnerable to this issue. In order to exploit this, the client needs access to the server, like the correct TLS certificates on the ig daemon case or access to the cluster in the Kubernetes case.
GHSA-PV22-FQCJ-7XWH has a CVSS score of 6.7 (Medium). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.40.0); upgrading removes the vulnerable code path.
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.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-PV22-FQCJ-7XWH? GHSA-PV22-FQCJ-7XWH is a medium-severity security vulnerability in github.com/inspektor-gadget/inspektor-gadget (go), affecting versions >= 0.31.0, < 0.40.0. It is fixed in 0.40.0.
- How severe is GHSA-PV22-FQCJ-7XWH? GHSA-PV22-FQCJ-7XWH has a CVSS score of 6.7 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of github.com/inspektor-gadget/inspektor-gadget are affected by GHSA-PV22-FQCJ-7XWH? github.com/inspektor-gadget/inspektor-gadget (go) versions >= 0.31.0, < 0.40.0 is affected.
- Is there a fix for GHSA-PV22-FQCJ-7XWH? Yes. GHSA-PV22-FQCJ-7XWH is fixed in 0.40.0. Upgrade to this version or later.
- Is GHSA-PV22-FQCJ-7XWH exploitable, and should I be worried? Whether GHSA-PV22-FQCJ-7XWH 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 GHSA-PV22-FQCJ-7XWH 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 GHSA-PV22-FQCJ-7XWH? Upgrade
github.com/inspektor-gadget/inspektor-gadgetto 0.40.0 or later.