Big Ip Next Cloud Native Network FunctionsApplication · F5
CVE-2025-54805
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWhen an iRule is configured on a virtual server via the declarative API, upon re-instantiation, the cleanup process can cause an increase in the Traffic Management Microkernel (TMM) memory resource utilization. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a memory resource exhaustion vulnerability in F5 BIG-IP where configuring an iRule on a virtual server via the declarative API (such as AS3) causes a memory leak in the TMM (Traffic Management Microkernel) during the cleanup process upon re-instantiation. Repeated re-instantiation can lead to elevated memory utilization, potentially degrading TMM performance and availability.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Big Ip Next Cloud Native Network FunctionsApplication
>= 1.1.0, <= 1.4.1
Big Ip Next For KubernetesApplication
= 2.0.0
Big Ip Next Service Proxy For KubernetesApplication
>= 1.7.0, <= 1.9.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the F5 product and versionRun 'tmsh show sys version' or check the management console for the installed F5 BIG-IP Next version. For Kubernetes deployments, check the version of the F5 Big Ip Next or Service Proxy For Kubernetes pods.Affected if The installed version falls within one of these ranges: Big Ip Next Cloud Native Network Functions >= 1.1.0 to <= 1.4.1, Big Ip Next For Kubernetes = 2.0.0, or Big Ip Next Service Proxy For Kubernetes >= 1.7.0 to <= 1.9.2
-
Verify if iRules are configured on virtual serversQuery the declarative API configuration or check the virtual server definitions for the presence of 'iRule' or 'rules' references in the JSON declaration.Affected if Any virtual server has an iRule assigned to it in the configuration deployed via declarative API (AS3)
-
Determine if configuration was applied via declarative APIReview deployment methods - check if the virtual server was created or modified using AS3 declarations, Terraform, or other declarative tooling rather than the traditional TMSH/GUI interface.Affected if The virtual servers with iRules were configured or updated using the declarative API (AS3)
-
Check for virtual server re-instantiation eventsReview TMM logs and audit logs for messages indicating virtual server re-instantiation, recreation, or reload events. Look for patterns of repeated deployments or configuration updates.Affected if Virtual servers with iRules have been re-instantiated multiple times since the iRule was applied via declarative API
You are affected if your F5 product version is in the affected range, you use iRules on virtual servers configured via declarative API, and those virtual servers have been re-instantiated multiple times, causing elevated TMM memory utilization.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataMonitor TMM memory utilization and avoid unnecessary re-instantiation of virtual servers with iRules configured via declarative API. Consider upgrading to a patched version once available. Avoid deploying iRules on EoTS versions.
Fix this in Big Ip Next Cloud Native Network Functions
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54805 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-54805 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data