How severe is GHSA-rp7v-4384-hfrp?

No CVSS score has been assigned to GHSA-rp7v-4384-hfrp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rp7v-4384-hfrp?

GHSA-rp7v-4384-hfrp affects the following packages: github.com/k8sgpt-ai/k8sgpt (Go). Ecosystems affected: Go.

How do I fix GHSA-rp7v-4384-hfrp?

Update github.com/k8sgpt-ai/k8sgpt to 0.4.32 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rp7v-4384-hfrp is resolved across your whole dependency graph.

How do I detect GHSA-rp7v-4384-hfrp in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/k8sgpt-ai/k8sgpt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-rp7v-4384-hfrp if there is no patch (or I can't update yet)?

Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Is GHSA-rp7v-4384-hfrp actively exploited in the wild?

No public exploit code has been indexed for GHSA-rp7v-4384-hfrp yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-rp7v-4384-hfrp published, and has it been updated?

GHSA-rp7v-4384-hfrp was published on April 24, 2026 and was last updated on June 25, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

k8sGPT has Prompt Injection through its k8sGPT-OperatorGHSA-rp7v-4384-hfrp

GHSA-rp7v-4384-hfrp is a remote code execution vulnerability in github.com/k8sgpt-ai/k8sgpt. A fix is available for github.com/k8sgpt-ai/k8sgpt — see the affected versions and patch details below.

Also known asGO-2026-5631

Published

Apr 24, 2026

Updated

Jun 25, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jun 25, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹github.com/k8sgpt-ai/k8sgpt

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/k8sgpt-ai/k8sgpt`	all versions	0.4.32`go get github.com/k8sgpt-ai/k8sgpt@v0.4.32`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/k8sgpt-ai/k8sgpt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/k8sgpt-ai/k8sgpt to 0.4.32 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rp7v-4384-hfrp is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is GHSA-rp7v-4384-hfrp in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works