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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-rp7v-4384-hfrp?

O3 pinpoints whether GHSA-rp7v-4384-hfrp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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 May 5, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-rp7v-4384-hfrp: k8sGPT has Prompt Injection through its k8…

Blast Radius

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

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-rp7v-4384-hfrp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-rp7v-4384-hfrp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 detects GHSA-rp7v-4384-hfrp across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-rp7v-4384-hfrp