k8sGPT has Prompt Injection through its k8sGPT-Operator

published 2026-04-24 6mo ago modified 2026-06-25 4mo ago also GO-2026-5631

cvss: —; not scored
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

### 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.

Patch / fix

fixed in 1

go github.com/k8sgpt-ai/k8sgpt 0.4.32

Is GHSA-rp7v-4384-hfrp in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem	package	affected	fixed in
go	github.com/k8sgpt-ai/k8sgpt	<0.4.32	0.4.32

Classification

Weakness

CWE-20 Improper Input Validation
CWE-502 Deserialization of Untrusted Data
CWE-915 Improperly Controlled Modification of Dynamically-Determined Object Attributes

References

github.com /k8sgpt-ai/k8sgpt/security/advisories/GHSA-rp7v-4384-hfrp
web, advisory
github.com /k8sgpt-ai/k8sgpt
package

Sources

GitHub Advisory GHSA-rp7v-4384-hfrp
OSV GO-2026-5631

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.