k8sGPT has Prompt Injection through its k8sGPT-Operator

Severity: high · Published 2026-04-24

### Summary In the auto-remediation pipeline, `object_to_execution.go` was deserializing the AI-generated YAML directly into a Deployment object, but there was lack of validation from the original Deployment object.

### Details This issue was fixed after coordination with Alex Jones.

### PoC To minimize the impact, the PoC of this vulnerability wasn't released, but was shared with the maintainers.

Technologies: github.com/k8sgpt-ai/k8sgpt (Go). Vendors: Go.

Quick answers

Is This vulnerability exploited in the wild?
No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?
High severity, published 24 April 2026.
Which products and versions are affected?
github.com/k8sgpt-ai/k8sgpt (Go) < 0.4.32.
Is there a fix for This vulnerability?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected?
Check whether you run github.com/k8sgpt-ai/k8sgpt (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Affected products

  • github.com/k8sgpt-ai/k8sgpt (Go) < 0.4.32

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.