CVE-2025-24319
Published: 05 February 2025
Summary
CVE-2025-24319 is a high-severity Improper Input Validation (CWE-20) vulnerability in F5 Big-Ip Next Central Manager. Its CVSS base score is 7.1 (High).
Operationally, ranked in the top 25.3% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
CVE-2025-24319 is an improper input validation issue in F5 BIG-IP Next Central Manager. When the product is running, specially crafted but undisclosed requests sent to its API cause the Kubernetes service on the BIG-IP Next Central Manager Node to terminate, producing a denial-of-service condition. The vulnerability is tracked under CWE-20 and carries a CVSS 4.0 score of 7.1 with high availability impact.
An attacker with low-privileged network access to the Central Manager API can trigger the flaw remotely without user interaction, resulting in repeated termination of the Kubernetes service and loss of management functionality for affected deployments. No authentication beyond the low-privilege requirement is needed, and the attack does not affect confidentiality or integrity.
The vendor advisory K000148412 at my.f5.com details mitigation steps and affected versions; software that has reached End of Technical Support is outside the scope of evaluation. EPSS remains low, with a current value of 0.0081 and a recorded peak of only 0.0106.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-3673
Vulnerability details
When BIG-IP Next Central Manager is running, undisclosed requests to the BIG-IP Next Central Manager API can cause the BIG-IP Next Central Manager Node's Kubernetes service to terminate. Note: Software versions which have reached End of Technical Support (EoTS) are…
more
not evaluated.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Security testing and developer training directly verify and enforce proper input validation, reducing exploitability of injection and malformed-data weaknesses.
Security testing and evaluation at multiple SDLC stages directly detects missing or flawed input validation, with the required remediation process ensuring fixes are applied.
Directly implements checks on information inputs to reject invalid data before processing.
Spam protection mechanisms perform filtering and detection on inbound/outbound messages, directly compensating for missing or weak input validation of unsolicited content.