Cette page n'a pas encore été traduite dans votre langue. Affichage du contenu en anglais pendant que nous y travaillons.

💡 Keep dependencies up to date — most exploits target known, patchable vulnerabilities.

HIGHCVE-2026-39458CVSS 7.5

CVE-2026-39458: DoS in F5 BIG-IP DNS Cache

Plateforme

linux

Composant

bigip

Corrigé dans

21.0.0.1

Traduction vers votre langue…

CVE-2026-39458 describes a denial-of-service (DoS) vulnerability within F5 BIG-IP's DNS cache functionality. When a BIG-IP DNS profile with DNS cache enabled is configured on a virtual server, specially crafted traffic can trigger a crash in the Traffic Management Microkernel (TMM), resulting in service unavailability. This vulnerability impacts versions 16.1.0 through 21.0.0.1, and a fix is available in version 21.0.0.1.

Impact et Scénarios d'Attaquetraduction en cours…

The primary impact of CVE-2026-39458 is a denial-of-service condition. An attacker can exploit this vulnerability by sending malicious DNS requests to the affected BIG-IP system. Successful exploitation leads to TMM termination, which disrupts all traffic managed by that virtual server. This can result in significant downtime and impact critical applications and services relying on the BIG-IP infrastructure. The blast radius extends to any service or application dependent on the affected virtual server, potentially impacting a wide range of users and systems. While the vulnerability doesn't directly lead to data exfiltration or code execution, the service disruption can be a significant operational and business impact.

Contexte d'Exploitationtraduction en cours…

CVE-2026-39458 is currently not listed on KEV (Known Exploited Vulnerabilities). The EPSS (Exploit Prediction Scoring System) score is pending evaluation. No public proof-of-concept (POC) code has been publicly released as of the publication date. CISA and F5 have published advisories regarding this vulnerability. Active exploitation campaigns are not currently confirmed, but the ease of sending DNS requests suggests a potential for opportunistic attacks.

Renseignement sur les Menaces

Statut de l'Exploit

Preuve de ConceptInconnu
CISA KEVNO
Exposition InternetÉlevée

CISA SSVC

Exploitationnone
Automatisableyes
Impact Techniquepartial

Vecteur CVSS

RENSEIGNEMENT SUR LES MENACES· CVSS 3.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H7.5HIGHAttack VectorNetworkComment l'attaquant atteint la cibleAttack ComplexityLowConditions requises pour exploiterPrivileges RequiredNoneNiveau d'authentification requisUser InteractionNoneSi une action de la victime est requiseScopeUnchangedImpact au-delà du composant affectéConfidentialityNoneRisque d'exposition de données sensiblesIntegrityNoneRisque de modification non autorisée de donnéesAvailabilityHighRisque d'interruption de servicenextguardhq.com · Score de base CVSS v3.1
Que signifient ces métriques?
Attack Vector
Réseau — exploitable à distance via internet. Aucun accès physique ou local requis.
Attack Complexity
Faible — aucune condition spéciale requise. Exploitable de manière fiable.
Privileges Required
Aucun — sans authentification. Aucune identifiant requis pour exploiter.
User Interaction
Aucune — attaque automatique et silencieuse. La victime ne fait rien.
Scope
Inchangé — impact limité au composant vulnérable.
Confidentiality
Aucun — aucun impact sur la confidentialité.
Integrity
Aucun — aucun impact sur l'intégrité.
Availability
Élevé — panne complète ou épuisement des ressources. Déni de service total.

Logiciel Affecté

Composantbigip
FournisseurF5
Version minimale16.1.0
Version maximale21.0.0.1
Corrigé dans21.0.0.1

Classification de Faiblesse (CWE)

Chronologie

  1. Réservé
  2. Publiée

Mitigation et Contournementstraduction en cours…

The recommended mitigation for CVE-2026-39458 is to upgrade to BIG-IP version 21.0.0.1 or later, which contains the fix. If immediate upgrade is not feasible, consider implementing temporary workarounds. One potential workaround involves rate-limiting DNS requests at the virtual server level to reduce the impact of malicious traffic. Additionally, deploying a Web Application Firewall (WAF) or reverse proxy in front of the BIG-IP can help filter out malicious DNS requests. Monitor BIG-IP system logs for unusual DNS activity and consider implementing intrusion detection signatures to identify potential exploitation attempts. After upgrading, confirm the fix by sending a series of crafted DNS requests to the system and verifying that TMM remains stable.

Comment corrigertraduction en cours…

Actualice su sistema BIG-IP a una versión corregida. Consulte la nota de seguridad de F5 (https://my.f5.com/manage/s/article/K000160945) para obtener información detallada sobre las versiones corregidas y los pasos de mitigación.

Questions fréquentestraduction en cours…

What is CVE-2026-39458 — DoS in F5 BIG-IP DNS Cache?

CVE-2026-39458 is a denial-of-service vulnerability in F5 BIG-IP's DNS cache. Malformed DNS traffic can crash the Traffic Management Microkernel (TMM), causing service disruption. It affects versions 16.1.0–21.0.0.1.

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

You are affected if you are running F5 BIG-IP versions 16.1.0 through 21.0.0.1 with a DNS profile enabled and DNS cache configured on a virtual server.

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

Upgrade to F5 BIG-IP version 21.0.0.1 or later to resolve the vulnerability. If immediate upgrade isn't possible, consider rate-limiting DNS requests or deploying a WAF.

Is CVE-2026-39458 being actively exploited?

Active exploitation campaigns are not currently confirmed, but the vulnerability's nature suggests a potential for opportunistic attacks. Monitor your systems closely.

Where can I find the official F5 advisory for CVE-2026-39458?

Refer to the official F5 Security Advisory: [https://www.f5.com/service/security-advisories/advisory/f5-security-advisory-39458](https://www.f5.com/service/security-advisories/advisory/f5-security-advisory-39458)

Ton projet est-il affecté ?

Téléverse ton fichier de dépendances et découvre instantanément si cette CVE et d'autres te touchent.

en directfree scan

Essayez maintenant — sans compte

scanZone.subtitle

Scan manuelSlack/email alertsContinuous monitoringWhite-label reports

Glissez-déposez votre fichier de dépendances

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