cve.bz

CVE-2025-61974 f5

8.7 highEPSS 0.5%Fix available

High (8.7) in f5. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
When a client SSL profile is configured on a virtual server, undisclosed requests can cause an increase in memory resource utilization.  Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Severity

CVSS 4.0

8.7 high
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

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 40th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2025-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-401 Missing Release of Memory after Effective Lifetime
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

  • F5 BIG-IP Next SPK: fixed in 2.1.0-EHF-1
  • F5 BIG-IP Next SPK: fixed in 2.0.2-EHF-2
  • F5 BIG-IP Next SPK: fixed in 2.0.0-EHF-2
  • F5 BIG-IP Next SPK: fixed in 1.7.14-EHF-2
  • F5 BIG-IP Next CNF: fixed in 2.1.0-EHF-1
  • F5 BIG-IP Next CNF: fixed in 2.0.2-EHF-2
  • F5 BIG-IP Next CNF: fixed in 2.0.0-EHF-2
  • F5 BIG-IP Next CNF: fixed in 1.4.0-EHF-3
  • Vendor advisory: https://my.f5.com/manage/s/article/K000156733

Ask an AI about this CVE

Show the promptExplain CVE-2025-61974 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-61974?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-61974?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-61974 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2025-61974

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2025-61974](https://cve.bz/cve/badge/CVE-2025-61974.svg)](https://cve.bz/cve/CVE-2025-61974)

HTML:

<a href="https://cve.bz/cve/CVE-2025-61974"><img src="https://cve.bz/cve/badge/CVE-2025-61974.svg" alt="CVE-2025-61974"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
F5 BIG-IPfrom 17.5.0 before 17.5.1.3
F5 BIG-IPfrom 17.1.0 before 17.1.3
F5 BIG-IPfrom 16.1.0 before 16.1.6.1
F5 BIG-IPfrom 15.1.0 before 15.1.10.8
F5 BIG-IP Next SPK2.0.0 and later
F5 BIG-IP Next SPK1.9.0 and later
F5 BIG-IP Next SPK1.8.0 and later
F5 BIG-IP Next SPK1.7.0 and later
F5 BIG-IP Next CNF2.0.0 and later
F5 BIG-IP Next CNF1.1.0 and later
F5 BIG-IP Next for Kubernetes2.0.0 and later

Fixed in

ProductFixed in
F5 BIG-IP Next SPK2.1.0-EHF-1
F5 BIG-IP Next SPK2.0.2-EHF-2
F5 BIG-IP Next SPK2.0.0-EHF-2
F5 BIG-IP Next SPK1.7.14-EHF-2
F5 BIG-IP Next CNF2.1.0-EHF-1
F5 BIG-IP Next CNF2.0.2-EHF-2
F5 BIG-IP Next CNF2.0.0-EHF-2
F5 BIG-IP Next CNF1.4.0-EHF-3
F5 BIG-IP Next for Kubernetes2.1.0-EHF-1

References

Check your stackJSON