Kubernetes ingress-nginx up to 1.13.6/1.14.1 Ingress Annotation unusual condition

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
3.0$0-$5k0.00

Summaryinfo

A vulnerability labeled as problematic has been found in Kubernetes ingress-nginx up to 1.13.6/1.14.1. The impacted element is an unknown function of the component Ingress Annotation Handler. Such manipulation leads to unusual condition. This vulnerability is documented as CVE-2026-24513. The attack can be executed remotely. There is not any exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in Kubernetes ingress-nginx up to 1.13.6/1.14.1. It has been rated as problematic. Affected by this issue is an unknown part of the component Ingress Annotation Handler. The manipulation with an unknown input leads to a unusual condition vulnerability. Using CWE to declare the problem leads to CWE-754. The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product. Impacted is confidentiality. CVE summarizes:

A security issue was discovered in ingress-nginx where the protection afforded by the `auth-url` Ingress annotation may not be effective in the presence of a specific misconfiguration. If the ingress-nginx controller is configured with a default custom-errors configuration that includes HTTP errors 401 or 403, and if the configured default custom-errors backend is defective and fails to respect the X-Code HTTP header, then an Ingress with the `auth-url` annotation may be accessed even when authentication fails. Note that the built-in custom-errors backend works correctly. To trigger this issue requires an administrator to specifically configure ingress-nginx with a broken external component.

The advisory is available at github.com. This vulnerability is handled as CVE-2026-24513 since 01/23/2026. The exploitation is known to be difficult. The attack may be launched remotely. The technical details are unknown and an exploit is not available.

The vulnerability scanner Nessus provides a plugin with the ID 297852 (Ingress-NGINX Controller < 1.13.7 / 1.14.x < 1.14.3 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 1.13.7 or 1.14.2 eliminates this vulnerability.

The vulnerability is also documented in the databases at Tenable (297852), EUVD (EUVD-2026-6096) and CERT Bund (WID-SEC-2026-0289). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Affected

  • Open Source Kubernetes

Productinfo

Type

Vendor

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.1
VulDB Meta Temp Score: 3.0

VulDB Base Score: 3.1
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍

CNA Base Score: 3.1
CNA Vector (kubernetes): 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Unusual condition
CWE: CWE-754
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 297852
Nessus Name: Ingress-NGINX Controller < 1.13.7 / 1.14.x < 1.14.3 Multiple Vulnerabilities

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: ingress-nginx 1.13.7/1.14.2

Timelineinfo

01/23/2026 CVE reserved
02/04/2026 +12 days Advisory disclosed
02/04/2026 +0 days VulDB entry created
02/18/2026 +13 days VulDB entry last update

Sourcesinfo

Advisory: 136679
Status: Confirmed

CVE: CVE-2026-24513 (🔒)
GCVE (CVE): GCVE-0-2026-24513
GCVE (VulDB): GCVE-100-344186
EUVD: 🔒
CERT Bund: WID-SEC-2026-0289 - Kubernetes (ingress-nginx): Mehrere Schwachstellen

Entryinfo

Created: 02/04/2026 07:44
Updated: 02/18/2026 00:31
Changes: 02/04/2026 07:44 (65), 02/05/2026 10:55 (7), 02/08/2026 12:49 (2), 02/18/2026 00:31 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!