Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

GHSA-fp9f-44c2-cw27

HIGH

GHSA-fp9f-44c2-cw27 is a high-severity (CVSS 7.6) Improper Input Validation vulnerability in k8s.io/ingress-nginx. 2 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-fp9f-44c2-cw27 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Ingress-nginx code injection via nginx.ingress.kubernetes.io/permanent-redirect annotation

Also known asCVE-2023-5044GO-2024-2428
Published
Oct 25, 2023
Updated
May 20, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
2 known

Real-World Exposure

1 pkg affected
🐹k8s.io/ingress-nginx

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

A security issue was identified in ingress-nginx where the nginx.ingress.kubernetes.io/permanent-redirect annotation on an Ingress object (in the networking.k8s.io or extensions API group) can be used to inject arbitrary commands, and obtain the credentials of the ingress-nginx controller. In the default configuration, that credential has access to all secrets in the cluster.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gok8s.io/ingress-nginxall versions1.9.0
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for k8s.io/ingress-nginx. 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.

  2. Fix

    Update k8s.io/ingress-nginx to 1.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fp9f-44c2-cw27 is resolved across your whole dependency graph.

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

  4. How O3 protects you

    O3 pinpoints whether GHSA-fp9f-44c2-cw27 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-fp9f-44c2-cw27. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A security issue was identified in [ingress-nginx](https://github.com/kubernetes/ingress-nginx) where the nginx.ingress.kubernetes.io/permanent-redirect annotation on an Ingress object (in the networking.k8s.io or extensions API group) can be used to inject arbitrary commands, and obtain the credentials of the ingress-nginx controller. In the default configuration, that credential has access to all secrets in the cluster.
O3 Security · Impact-Aware SCA

Is GHSA-fp9f-44c2-cw27 in your dependencies?

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