Home › Intelligence › Brief
VULNERABILITY BRIEF 🔴 Critical Vulnerability

Critical Remote Code Execution in F5 BIG‑IP (CVE‑2025‑53521) Actively Exploited

F5 BIG‑IP’s CVE‑2025‑53521, originally reported as a DoS flaw, is now confirmed as a remote code execution vulnerability with active exploitation. The bug affects multiple BIG‑IP versions and poses a severe supply‑chain risk for organizations that depend on F5 load‑balancing and security appliances.

Verisq™ Intelligence · 📅 March 31, 2026 · 📰 darkreading.com
🔴
Severity
Critical
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
1 sector(s)
✅
Actions
5 recommended
📰
Source
darkreading.com

Critical Remote Code Execution in F5 BIG‑IP (CVE‑2025‑53521) Actively Exploited

What It Is – A flaw in F5 BIG‑IP’s Traffic Management Operating System (TMOS) that was originally disclosed as a high‑severity denial‑of‑service issue has been re‑evaluated and confirmed to allow unauthenticated remote code execution (RCE). The vulnerability (CVE‑2025‑53521) can be triggered over HTTP/HTTPS, granting attackers full control of the appliance.

Exploitability – Public proof‑of‑concept code and multiple threat‑intel feeds indicate the vulnerability is being weaponised in the wild. CVSS v3.1 base score is 9.8 (Critical).

Affected Products – All F5 BIG‑IP versions prior to the emergency patches released in March 2025, including LTM, GTM, and ASM modules. Specific affected releases are listed in F5’s advisory (e.g., 16.1.x, 17.0.x, 18.1.x, 19.2.x).

TPRM Impact – Enterprises that rely on F5 BIG‑IP for load balancing, web‑application firewall, or DNS services expose their entire network surface to a compromised third‑party component. A successful RCE can be leveraged to pivot into downstream applications, exfiltrate data, or disrupt critical services, creating a supply‑chain risk that extends to customers and partners.

Recommended Actions –

  1. Apply F5’s emergency patches immediately (or upgrade to a fixed version).
  2. Enable the temporary mitigation published by F5 (IP‑based access controls, disabling unused virtual servers).
  3. Conduct a rapid inventory of all BIG‑IP appliances across the organization and any managed service providers.
  4. Monitor logs for anomalous traffic to the BIG‑IP management interface (unexpected HTTP methods, outbound connections from the appliance).
  5. Validate segmentation – ensure the BIG‑IP control plane is isolated from sensitive data stores.

Source: Dark Reading – F5 BIG‑IP Vulnerability Reclassified as RCE, Under Exploitation

📰 Original Source
https://www.darkreading.com/application-security/fortinet-big-ip-vulnerability-reclassified-rce-exploitation ↗

This Verisq Intelligence Brief is an independent analysis. Read the original reporting at the link above.

Vulnerability exposure

Is this CVE in your supply chain?

Verisq matches published vulnerabilities against the software your vendors run, so you know which relationships this touches before the next review.

See vendor exposure →