Análisis pendienteCVE-2026-41953

CVE-2026-41953: Privilege Escalation in F5 BIG-IP

Plataforma

linux

Componente

bigip

Corregido en

21.0.0.2

CVE-2026-41953 describes a privilege escalation vulnerability within F5 BIG-IP systems. A successful exploit allows a highly privileged, authenticated attacker—specifically one possessing the Resource Administrator role—to modify configuration objects, leading to unauthorized privilege elevation. This vulnerability impacts BIG-IP versions ranging from 16.1.0 through 21.0.0.2. The vulnerability has been resolved in version 21.0.0.2.

Impacto y Escenarios de Ataquetraduciendo…

The impact of CVE-2026-41953 is significant due to the potential for complete system compromise. An attacker who can successfully exploit this vulnerability gains the ability to modify critical configuration settings, potentially enabling them to bypass security controls, access sensitive data, and execute arbitrary code with elevated privileges. This could lead to data breaches, denial of service, or complete control over the affected BIG-IP system. The Resource Administrator role already holds considerable power, and this vulnerability amplifies that power, allowing for actions beyond the intended scope of that role. The ability to modify configuration objects opens the door to a wide range of malicious activities, effectively granting the attacker root-level access.

Contexto de Explotacióntraduciendo…

CVE-2026-41953 was published on May 13, 2026. Its severity is rated HIGH with a CVSS score of 8.7. As of this writing, there are no publicly available proof-of-concept exploits. The vulnerability is not currently listed on KEV or EPSS, suggesting a low to medium probability of active exploitation. Monitor F5's security advisories and CISA bulletins for updates regarding potential exploitation campaigns.

Inteligencia de Amenazas

Estado del Exploit

Prueba de ConceptoDesconocido
CISA KEVNO
Exposición en InternetAlta

CISA SSVC

Explotaciónnone
Automatizableno
Impacto Técnicototal

Vector CVSS

INTELIGENCIA DE AMENAZAS· CVSS 3.1CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N8.7HIGHAttack VectorNetworkCómo el atacante alcanza el objetivoAttack ComplexityLowCondiciones necesarias para explotarPrivileges RequiredHighNivel de autenticación requeridoUser InteractionNoneSi la víctima debe realizar una acciónScopeChangedImpacto más allá del componente afectadoConfidentialityHighRiesgo de exposición de datos sensiblesIntegrityHighRiesgo de modificación no autorizada de datosAvailabilityNoneRiesgo de interrupción del servicionextguardhq.com · Puntuación Base CVSS v3.1
¿Qué significan estas métricas?
Attack Vector
Red — explotable remotamente por internet. Sin acceso físico ni local. Mayor superficie de ataque.
Attack Complexity
Baja — sin condiciones especiales. El atacante puede explotar de forma confiable sin configuraciones raras.
Privileges Required
Alto — se requiere cuenta de administrador o privilegiada.
User Interaction
Ninguna — el ataque es automático y silencioso. La víctima no hace nada.
Scope
Cambiado — el ataque puede pivotar a otros sistemas más allá del componente vulnerable.
Confidentiality
Alto — pérdida total de confidencialidad. El atacante puede leer todos los datos.
Integrity
Alto — el atacante puede escribir, modificar o eliminar cualquier dato.
Availability
Ninguno — sin impacto en disponibilidad.

Software Afectado

Componentebigip
ProveedorF5
Versión mínima16.1.0
Versión máxima21.0.0.2
Corregido en21.0.0.2

Clasificación de Debilidad (CWE)

Cronología

  1. Reservado
  2. Publicada

Mitigación y Workaroundstraduciendo…

The primary mitigation for CVE-2026-41953 is to upgrade to F5 BIG-IP version 21.0.0.2 or later. If immediate upgrade is not feasible, consider implementing stricter access controls to limit the number of users with the Resource Administrator role. Review existing configurations for any unusual or suspicious changes that may indicate exploitation. While a WAF or proxy cannot directly prevent this vulnerability, it can help detect and block malicious requests attempting to exploit it. Monitor BIG-IP logs for any unauthorized configuration modifications. After upgrading, verify the fix by attempting to modify a configuration object with a non-administrative user account and confirming that the action is denied.

Cómo corregirlotraduciendo…

Actualice a una versión corregida de F5 BIG-IP. Las versiones corregidas son 21.0.0.2, 17.5.1.6 y 17.1.3.2. Consulte la documentación de F5 para obtener instrucciones detalladas sobre cómo actualizar.

Preguntas frecuentestraduciendo…

What is CVE-2026-41953 — Privilege Escalation in F5 BIG-IP?

CVE-2026-41953 is a HIGH severity vulnerability affecting F5 BIG-IP versions 16.1.0–21.0.0.2. It allows an authenticated attacker with the Resource Administrator role to escalate privileges by modifying configuration objects, potentially leading to system compromise.

Am I affected by CVE-2026-41953 in F5 BIG-IP?

If you are running F5 BIG-IP versions 16.1.0 through 21.0.0.2, you are potentially affected. Check your version and upgrade as soon as possible to mitigate the risk.

How do I fix CVE-2026-41953 in F5 BIG-IP?

The recommended fix is to upgrade to F5 BIG-IP version 21.0.0.2 or later. If immediate upgrade is not possible, implement stricter access controls and monitor logs for suspicious activity.

Is CVE-2026-41953 being actively exploited?

As of the current assessment, there are no publicly available exploits and no reports of active exploitation. However, the vulnerability's severity warrants proactive mitigation.

Where can I find the official F5 BIG-IP advisory for CVE-2026-41953?

Refer to the official F5 Security Advisories page for the latest information and updates regarding CVE-2026-41953: [https://www.f5.com/services/security-advisories](https://www.f5.com/services/security-advisories)

¿Tu proyecto está afectado?

Sube tu archivo de dependencias y detecta esta y otras CVEs al instante.

liveescaneo gratuito

Pruébalo ahora — sin cuenta

Sube cualquier manifiesto (composer.lock, package-lock.json, lista de plugins WordPress…) o pega tu lista de componentes. Recibís un reporte de vulnerabilidades al instante. Subir un archivo es solo el primer paso: con una cuenta tenés monitoreo continuo, alertas en tu canal, multi-proyecto y reportes white-label.

Escaneo manualAlertas en Slack/emailMonitoreo continuoReportes white-label

Arrastra y suelta tu archivo de dependencias

composer.lock, package-lock.json, requirements.txt, Gemfile.lock, pubspec.lock, Dockerfile...