{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2025-54805 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-54805 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-54805 is a medium-severity denial of service vulnerability in F5 BIG-IP Next CNF, published on 15 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-54805 and fix it if it is affected.\n\nWhat it is: CVE-2025-54805 is a medium-severity denial of service vulnerability in F5 BIG-IP Next CNF, published on 15 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-54805 in the wild and no public exploit code.\n\nAffected product: F5 BIG-IP Next CNF. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-54805/ (Markdown: https://insights.sbomify.com/CVE-2025-54805/index.md)","id":"CVE-2025-54805","markdown":"https://insights.sbomify.com/CVE-2025-54805/index.md","name":"CVE-2025-54805","record":{"aliases":["GHSA-vgh4-q2cm-w7mg"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"F5 BIG-IP Next","requires_auth":"low_privilege","summary":"Re-instantiating virtual servers with iRules via declarative API causes TMM memory leaks, potentially leading to denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"f5","cpe":[{"product":"big-ip_next_cloud-native_network_functions","vendor":"f5"},{"product":"big-ip_next_for_kubernetes","vendor":"f5"},{"product":"big-ip_next_service_proxy_for_kubernetes","vendor":"f5"}],"cvss":{"score":6,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L","version":"4.0"},"cwes":[{"id":"CWE-401","name":"Missing Release of Memory after Effective Lifetime"}],"description":"When 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"TMM Vulnerability","id":"CVE-2025-54805","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in GROWI","id":"CVE-2025-54806"},"packages":[],"prev":{"headline":"Russh is missing an overflow check during channel windows adjust","id":"CVE-2025-54804"},"products":["BIG-IP Next CNF","BIG-IP Next SPK","BIG-IP Next for Kubernetes"],"published":"2025-10-15","related":[{"cvss_score":8.7,"headline":"BIG-IP HTTP/2 vulnerability","id":"CVE-2026-59762","kev_date_added":null,"published":"2026-07-15"},{"cvss_score":8.7,"headline":"BIG-IP PEM vulnerability","id":"CVE-2025-54479","kev_date_added":null,"published":"2025-10-15"},{"cvss_score":8.7,"headline":"BIG-IP Next (CNF, SPK, and Kubernetes) vulnerability","id":"CVE-2025-58120","kev_date_added":null,"published":"2025-10-15"},{"cvss_score":8.7,"headline":"BIG-IP SSL/TLS vulnerability","id":"CVE-2025-60016","kev_date_added":null,"published":"2025-10-15"},{"cvss_score":8.7,"headline":"BIG-IP SSL/TLS vulnerability","id":"CVE-2025-61974","kev_date_added":null,"published":"2025-10-15"},{"cvss_score":7.1,"headline":"BIG-IP Next (CNF, SPK, and Kubernetes) vulnerability","id":"CVE-2025-55670","kev_date_added":null,"published":"2025-10-15"},{"cvss_score":7.1,"headline":"BIG-IP Next CNF \u0026 SPK vulnerability","id":"CVE-2024-23306","kev_date_added":null,"published":"2024-02-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["F5"]},"summary":"Re-instantiating virtual servers with iRules via declarative API causes TMM memory leaks, potentially leading to denial of service.","url":"https://insights.sbomify.com/CVE-2025-54805/"}