{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2025-58120 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-58120 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-58120 is a high-severity vulnerability in F5 BIG-IP Next CNF, published on 15 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-58120 and fix it if it is affected.\n\nWhat it is: CVE-2025-58120 is a high-severity vulnerability in F5 BIG-IP Next CNF, published on 15 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-58120 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-58120/ (Markdown: https://insights.sbomify.com/CVE-2025-58120/index.md)","id":"CVE-2025-58120","markdown":"https://insights.sbomify.com/CVE-2025-58120/index.md","name":"CVE-2025-58120","record":{"aliases":["GHSA-jg4r-5fpx-73gm"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"BIG-IP Next","requires_auth":"none","summary":"Attackers can cause a denial of service by triggering a null dereference in the Traffic Management Microkernel when HTTP/2 Ingress is enabled.","user_interaction":"not_required","vuln_class":"null_dereference"},"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":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"When HTTP/2 Ingress is configured, undisclosed traffic can cause the Traffic Management Microkernel (TMM) to terminate.  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":"BIG-IP Next (CNF, SPK, and Kubernetes) vulnerability","id":"CVE-2025-58120","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Insufficient permission validation on multiple REST API endpoints","id":"CVE-2025-58121"},"packages":[],"prev":{"headline":"Command injection in WN-7D36QR","id":"CVE-2025-58116"},"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 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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["F5"]},"summary":"Attackers can cause a denial of service by triggering a null dereference in the Traffic Management Microkernel when HTTP/2 Ingress is enabled.","url":"https://insights.sbomify.com/CVE-2025-58120/"}