Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-59762: When an HTTP/2 profile is configured on a virtual server, undisclosed requests can cause an increase in memory

48
This month
HIGH 7.5REMOTEWATCHLISTUPGRADEUPGRADEUPGRADE

CVE-2026-59762 is a high-severity flaw (CVSS 7.5) affecting big-ip next cloud-native network functions, big-ip next for kubernetes, big-ip next service proxy for kubernetes. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

When an HTTP/2 profile is configured on a virtual server, undisclosed requests can cause an increase in memory resource utilization.   Impact: System performance can degrade until the TMM process is either forced to restart or is manually restarted. This vulnerability allows a remote, unauthenticated attacker to cause a degradation of service that can lead to a denial-of-service (DoS) on the BIG-IP system. There is no control plane expos

Why this priority

  • High severity
  • Remotely exploitable, no login, no user action
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score7.5 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.6% (top 53%)
CISA exploited listNo
WeaknessCWE-770
Published2026-07-15
Last modified2026-08-06
Publisher (CNA): F5 Networks · Vendor: f5

Share: LinkedIn · X · Reddit

Last updated 2026-08-06 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

f5 big-ip next cloud-native network functions UPGRADE
Affected: >= 1.1.0 and < 1.4.3 · >= 2.0.0 and < 2.2.3 · 2.3.0
Fixed in: 1.4.3, 2.2.3
Safe to downgrade to: a release before 1.1.0
1. Check installed version
apt-cache policy big-ip-next-cloud-native-network-functions || rpm -q big-ip-next-cloud-native-network-functions || big-ip-next-cloud-native-network-functions --version
2. UPGRADE to 1.4.3 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade big-ip-next-cloud-native-network-functions
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade big-ip-next-cloud-native-network-functions
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 1.1.0 (Debian / Ubuntu)
apt-cache madison big-ip-next-cloud-native-network-functions sudo apt install big-ip-next-cloud-native-network-functions=<VERSION_BEFORE_1.1.0> sudo apt-mark hold big-ip-next-cloud-native-network-functions
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list big-ip-next-cloud-native-network-functions sudo dnf downgrade big-ip-next-cloud-native-network-functions-<VERSION_BEFORE_1.1.0> sudo dnf versionlock add big-ip-next-cloud-native-network-functions
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
f5 big-ip next for kubernetes UPGRADE
Affected: >= 2.0.0 and < 2.2.3 · 2.3.0
Fixed in: 2.2.3
Safe to downgrade to: a release before 2.0.0
1. Check installed version
apt-cache policy big-ip-next-for-kubernetes || rpm -q big-ip-next-for-kubernetes || big-ip-next-for-kubernetes --version
2. UPGRADE to 2.2.3 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade big-ip-next-for-kubernetes
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade big-ip-next-for-kubernetes
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 2.0.0 (Debian / Ubuntu)
apt-cache madison big-ip-next-for-kubernetes sudo apt install big-ip-next-for-kubernetes=<VERSION_BEFORE_2.0.0> sudo apt-mark hold big-ip-next-for-kubernetes
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list big-ip-next-for-kubernetes sudo dnf downgrade big-ip-next-for-kubernetes-<VERSION_BEFORE_2.0.0> sudo dnf versionlock add big-ip-next-for-kubernetes
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
f5 big-ip next service proxy for kubernetes UPGRADE
Affected: >= 1.7.0 and < 1.7.18 · >= 1.8.0 and <= 1.9.2 · >= 2.0.0 and <= 2.0.3
Fixed in: 1.7.18
Safe to downgrade to: a release before 1.7.0
1. Check installed version
apt-cache policy big-ip-next-service-proxy-for-kubernetes || rpm -q big-ip-next-service-proxy-for-kubernetes || big-ip-next-service-proxy-for-kubernetes --version
2. UPGRADE to 1.7.18 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade big-ip-next-service-proxy-for-kubernetes
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade big-ip-next-service-proxy-for-kubernetes
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 1.7.0 (Debian / Ubuntu)
apt-cache madison big-ip-next-service-proxy-for-kubernetes sudo apt install big-ip-next-service-proxy-for-kubernetes=<VERSION_BEFORE_1.7.0> sudo apt-mark hold big-ip-next-service-proxy-for-kubernetes
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list big-ip-next-service-proxy-for-kubernetes sudo dnf downgrade big-ip-next-service-proxy-for-kubernetes-<VERSION_BEFORE_1.7.0> sudo dnf versionlock add big-ip-next-service-proxy-for-kubernetes
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-59762?

big-ip next cloud-native network functions: upgrade to 1.4.3, 2.2.3; big-ip next for kubernetes: upgrade to 2.2.3; big-ip next service proxy for kubernetes: upgrade to 1.7.18. Exact commands for each OS are on this page.

Is CVE-2026-59762 being exploited?

CVE-2026-59762 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-59762 affect?

CVE-2026-59762 affects big-ip next cloud-native network functions, big-ip next for kubernetes, big-ip next service proxy for kubernetes. Severity is high (CVSS 7.5). When an HTTP/2 profile is configured on a virtual server, undisclosed requests can cause an increase in memory resource utilization.   Impact: System performance can degrade until the TMM process is either forced to restart or is m

How urgent is CVE-2026-59762?

Priority 48/100. High severity; Remotely exploitable, no login, no user action; On your watchlist

Software pages

Kubernetes vulnerabilities · F5 BIG-IP vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.