dbcve.org
Nginx Ingress ControllerWeb server / proxy · F5

CVE-2025-14727

HIGH · 8.3 CVSS v3.1 Published 2025-12-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability exists in NGINX Ingress Controller's nginx.org/rewrite-target annotation validation. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

NGINX Ingress Controller contains a validation flaw in processing the nginx.org/rewrite-target annotation, allowing potentially malicious or unexpected rewrite targets to be accepted. This could enable attackers to manipulate request routing, possibly leading to path traversal or unauthorized redirection.

MitigationImplement strict validation for the rewrite-target annotation, using allowlist patterns and input sanitization to ensure only intended rewrite targets are permitted.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Nginx Ingress ControllerWeb server / proxy
Affected:= 5.3.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine NGINX Ingress Controller version
    Run 'kubectl get pods -n <ingress-namespace> -o jsonpath="{.items[*].spec.containers[*].image}"' or check your deployment manifests for the nginx-ingress-controller image tag
    Affected if The installed version is exactly 5.3.0
  2. Identify Ingress resources using rewrite-target annotation
    Run 'kubectl get ingress --all-namespaces -o json | jq -r '.items[] | select(.metadata.annotations["nginx.org/rewrite-target"] != null) | {name: .metadata.name, namespace: .metadata.namespace, annotation: .metadata.annotations["nginx.org/rewrite-target"]}''
    Affected if Any Ingress resource has the nginx.org/rewrite-target annotation defined
  3. Inspect rewrite-target annotation values for path traversal patterns
    Review the annotation values from the previous step. Look for patterns containing '..' (double dots), absolute paths starting with '/', or external redirect indicators
    Affected if The rewrite-target value contains '..' or other path traversal sequences, or redirects to unexpected absolute paths
  4. Check Ingress controller logs for suspicious rewrite behavior
    Review Ingress controller logs for unusual rewrite patterns or failed validation attempts. Run 'kubectl logs -n <ingress-namespace> <ingress-controller-pod>' and search for rewrite-target related entries
    Affected if Logs show unexpected rewrite targets being processed or validation failures
  5. Audit all Ingress resources in the cluster
    List all Ingress resources with 'kubectl get ingress --all-namespaces -o yaml' and manually review each for the nginx.org/rewrite-target annotation
    Affected if Any Ingress with rewrite-target exists in a version 5.3.0 controller environment

You are affected if running NGINX Ingress Controller version 5.3.0 AND any Ingress resource uses the nginx.org/rewrite-target annotation with potentially malicious values containing path traversal sequences.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict validation for the rewrite-target annotation, using allowlist patterns and input sanitization to ensure only intended rewrite targets are permitted.

Fix this in Nginx Ingress Controller Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14727 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-14727 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data