# CVE-2023-5044: Code injection via nginx.ingress.kubernetes.io/permanent-redirect annotation

> Attackers can execute arbitrary code by injecting malicious payloads into the permanent-redirect annotation of Kubernetes ingress resources.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Oct 2023
- **Updated:** 12 Jun 2025
- **Also known as:** GHSA-fp9f-44c2-cw27, GO-2024-2428, MINI-2332-qhrh-8frv, MINI-37j5-588g-r59j, MINI-387g-72cj-rcp8, MINI-3p33-v4vv-crr3, MINI-9fv2-p24q-pgx5, MINI-hh7m-gg2f-m737, MINI-j5fh-7hgx-r7wg, MINI-jqc2-526f-2ww2, MINI-vxr8-83rq-xpxc, MINI-wxr4-849f-xgmv

## What is CVE-2023-5044?

CVE-2023-5044 is a high-severity code injection vulnerability in Kubernetes ingress-nginx, published on 25 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2023-5044?

3 open source packages ship an affected version, including k8s.io/ingress-nginx. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `k8s.io/ingress-nginx` | Go | All versions | None |
| `k8s.io/ingress-nginx` | Go | All versions | 1.9.0 |
| `k8s.io/ingress-nginx` | Go | All versions | 1.9.0 |

Products: Kubernetes Ingress-Nginx.

## How do I fix CVE-2023-5044?

Upgrade k8s.io/ingress-nginx to 1.9.0 or later.

## Is CVE-2023-5044 being exploited?

There is no known exploitation of CVE-2023-5044 in the wild and no public exploit code.

Public exploit code:

- PoC CVE-2023-5044 (github_poc): https://github.com/r0binak/CVE-2023-5044
- https://github.com/4ARMED/cve-2023-5044 (github_poc): https://github.com/4ARMED/cve-2023-5044
- Poc for CVE 2023 5044 (github_poc): https://github.com/KubernetesBachelor/CVE-2023-5044

## Other vulnerabilities in Kubernetes ingress-nginx

- [CVE-2026-3288](https://insights.sbomify.com/CVE-2026-3288/): ingress-nginx rewrite-target nginx configuration injection (high 8.8)
- [CVE-2022-4886](https://insights.sbomify.com/CVE-2022-4886/): Ingress-nginx `path` sanitization can be bypassed with `log_format` directive (high 8.8)
- [CVE-2023-5043](https://insights.sbomify.com/CVE-2023-5043/): Ingress nginx annotation injection causes arbitrary command execution (high 7.6)
- [CVE-2021-25748](https://insights.sbomify.com/CVE-2021-25748/): Ingress-nginx `path` sanitization can be bypassed with newline character (high 7.6)
- [CVE-2021-25745](https://insights.sbomify.com/CVE-2021-25745/): Ingress-nginx path can be pointed to service account token file (high 7.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-5044 and fix it if it is affected.

What it is: CVE-2023-5044 is a high-severity code injection vulnerability in Kubernetes ingress-nginx, published on 25 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-5044 in the wild and no public exploit code.

Affected packages and fixed versions:
- k8s.io/ingress-nginx (Go): affected all versions; no fix listed
- k8s.io/ingress-nginx (Go): affected all versions; fixed in 1.9.0
- k8s.io/ingress-nginx (Go): affected all versions; fixed in 1.9.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-5044/ (Markdown: https://insights.sbomify.com/CVE-2023-5044/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-5044
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-5044
- OSV: https://osv.dev/vulnerability/CVE-2023-5044

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-5044/
Summaries are generated and may contain mistakes; the official description above is the record.