Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

Ingress-NGINX Admission Controller v1.11.1 - FD Injection to RCE

0
Critical
Published: Wed Feb 04 2026 (02/04/2026, 00:00:00 UTC)
Source: Exploit-DB RSS Feed

Description

A critical remote code execution (RCE) vulnerability exists in Ingress-NGINX Admission Controller version 1. 11. 1, caused by file descriptor (FD) injection. This flaw allows attackers to inject malicious file descriptors, leading to arbitrary code execution on the affected system without authentication or user interaction. The exploit code is publicly available and written in C, increasing the risk of weaponization. No official patches or fixes have been released yet. European organizations using this specific version of the Ingress-NGINX Admission Controller in their Kubernetes environments are at significant risk, especially those in countries with high cloud-native adoption. The vulnerability impacts confidentiality, integrity, and availability, making it critical to implement immediate mitigations such as isolating vulnerable components, monitoring for suspicious activity, and applying any available workarounds. Countries like Germany, the UK, France, and the Netherlands are likely most affected due to their extensive use of Kubernetes and cloud infrastructure. Organizations should prioritize upgrading once patches are available and restrict network access to the admission controller to minimize exposure.

AI-Powered Analysis

AILast updated: 02/05/2026, 09:08:45 UTC

Technical Analysis

The Ingress-NGINX Admission Controller version 1.11.1 contains a critical vulnerability that enables file descriptor (FD) injection, which can be exploited to achieve remote code execution (RCE). The admission controller is a Kubernetes component that validates and mutates ingress resource configurations, playing a crucial role in managing inbound traffic to cluster services. The vulnerability arises from improper handling of file descriptors, allowing an attacker to inject malicious descriptors that the controller processes, leading to arbitrary code execution within the Kubernetes control plane context. This flaw does not require authentication or user interaction, making it highly exploitable in exposed environments. The exploit code, written in C, is publicly available on Exploit-DB (ID 52475), facilitating rapid weaponization by attackers. No patches or official mitigations have been published at the time of disclosure, increasing the urgency for defensive measures. The vulnerability threatens the confidentiality, integrity, and availability of Kubernetes clusters by potentially allowing attackers to execute arbitrary commands, escalate privileges, or disrupt ingress traffic management. Given the widespread adoption of Kubernetes and Ingress-NGINX in cloud-native deployments, this vulnerability poses a significant risk to organizations relying on these technologies.

Potential Impact

For European organizations, this vulnerability can lead to severe consequences including unauthorized access to sensitive data, disruption of critical services, and potential lateral movement within the network. Compromise of the admission controller can undermine the security of the entire Kubernetes cluster, affecting applications and services running in production. This can result in data breaches, service outages, and reputational damage. Organizations in sectors such as finance, healthcare, and government, which heavily rely on Kubernetes for scalable and secure deployments, face heightened risks. The availability of exploit code lowers the barrier for attackers, increasing the likelihood of targeted attacks or widespread exploitation. Additionally, the lack of patches means organizations must rely on mitigations that may not fully eliminate risk, prolonging exposure. The impact extends beyond individual organizations to supply chains and critical infrastructure that depend on Kubernetes orchestration.

Mitigation Recommendations

Immediate mitigation steps include isolating the Ingress-NGINX Admission Controller from untrusted networks and restricting access to the Kubernetes API server to trusted administrators only. Implement network segmentation and firewall rules to limit exposure of the admission controller. Enable comprehensive logging and monitoring to detect anomalous activities related to file descriptor manipulation or unexpected process behavior. Employ runtime security tools and Kubernetes security policies (e.g., Pod Security Policies, admission webhooks) to enforce strict controls on ingress resource modifications. Until an official patch is released, consider deploying compensating controls such as disabling the vulnerable admission controller if feasible or using alternative ingress controllers with no known vulnerabilities. Regularly review and update Kubernetes components and dependencies to ensure timely application of security updates. Engage with the Kubernetes and Ingress-NGINX communities for updates and recommended best practices. Conduct thorough incident response preparedness to quickly address any exploitation attempts.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Edb Id
52475
Has Exploit Code
true
Code Language
c

Indicators of Compromise

Exploit Source Code

Exploit Code

Exploit code for Ingress-NGINX Admission Controller v1.11.1 - FD Injection to RCE

# Exploit Title:  Ingress-NGINX Admission Controller v1.11.1 - FD Injection to RCE 
# Date: 2025-10-07
# Exploit Author: Beatriz Fresno Naumova
# Vendor Homepage: https://kubernetes.io
# Software Link: https://github.com/kubernetes/ingress-nginx
# Version: Affects v1.10.0 to v1.11.1 (potentially others)
# Tested on: Ubuntu 22.04, RKE2 Kubernetes Cluster
# CVE: CVE-2025-1097, CVE-2025-1098, CVE-2025-24514, CVE-2025-1974

import os
import sys
import socket
import requests
import threading
from url
... (4266 more characters)
Code Length: 4,766 characters • Language: C/C++

Threat ID: 69845ddcf9fa50a62f0fd4a1

Added to database: 2/5/2026, 9:07:40 AM

Last enriched: 2/5/2026, 9:08:45 AM

Last updated: 2/5/2026, 8:25:45 PM

Views: 9

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats