cve.bz

CVE-2026-40618 f5: Incorrect Calculation of Buffer Size

8.7 highEPSS 0.3%Fix available

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

On this page
When an SSL profile is configured on a virtual server on BIG-IP Virtual Edition (VE) without Intel QuickAssist Technology (QAT) or on BIG-IP hardware platforms with the database variable crypto.hwacceleration set to disabled, 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.

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:L

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.3% (unchanged from 0.3% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 26th 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 2026-05-13. 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-131 Incorrect Calculation of Buffer Size
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-40618 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-40618?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-40618?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-2026-40618 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-2026-40618

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-2026-40618](https://cve.bz/cve/badge/CVE-2026-40618.svg)](https://cve.bz/cve/CVE-2026-40618)

HTML:

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

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
F5 BIG-IPfrom 21.0.0 before 21.0.0.1
F5 BIG-IPfrom 17.5.0 before 17.1.5.4
F5 BIG-IPfrom 17.1.0 before 17.1.3.1
F5 BIG-IP16.1.0 and later
F5 BIG-IP Next SPK2.0.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 Kubernetesfrom 2.0.0 before 2.2.0

Fixed in

ProductFixed in
F5 BIG-IP21.1.0

Attack patterns (CAPEC)

  • CAPEC-47 Buffer Overflow via Parameter Expansion Likelihood: Medium · Severity: High
  • CAPEC-100 Overflow Buffers Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON