Pending AnalysisCVE-2026-32643

CVE-2026-32643: Privilege Escalation in F5 BIG-IP

Platform

linux

Component

bigip

Fixed in

21.0.0.2

CVE-2026-32643 describes a privilege escalation vulnerability within F5 BIG-IP and BIG-IQ systems. A successful exploit allows a highly privileged, authenticated attacker – specifically one possessing the Certificate Manager role – to modify configuration objects and ultimately execute arbitrary commands. This vulnerability impacts versions 16.1.0 through 21.0.0.2; a patch is available in version 21.0.0.2.

Impact and Attack Scenarios

The impact of CVE-2026-32643 is significant due to the potential for complete system compromise. An attacker who can leverage this vulnerability gains the ability to run arbitrary commands with elevated privileges, effectively bypassing standard security controls. This could lead to data exfiltration, system modification, denial of service, or even complete takeover of the affected BIG-IP or BIG-IQ instance. The Certificate Manager role, while privileged, is often granted to multiple administrators, expanding the potential attack surface. The ability to modify configuration objects is a critical pathway for attackers to establish persistent access or pivot to other systems within the network.

Exploitation Context

CVE-2026-32643 was published on May 13, 2026. Its severity is rated HIGH (CVSS: 8.7). Currently, there are no publicly available exploits or active campaigns targeting this vulnerability. The vulnerability is not listed on CISA KEV. The potential for exploitation remains, particularly given the relatively broad range of affected versions and the ease with which an authenticated attacker can leverage the Certificate Manager role.

Threat Intelligence

Exploit Status

Proof of ConceptUnknown
CISA KEVNO
Internet ExposureHigh

CISA SSVC

Exploitationnone
Automatableno
Technical Impacttotal

CVSS Vector

THREAT INTELLIGENCE· CVSS 3.1CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N8.7HIGHAttack VectorNetworkHow the attacker reaches the targetAttack ComplexityLowConditions required to exploitPrivileges RequiredHighAuthentication level needed to attackUser InteractionNoneWhether a victim must take actionScopeChangedImpact beyond the vulnerable componentConfidentialityHighRisk of sensitive data exposureIntegrityHighRisk of unauthorized data modificationAvailabilityNoneRisk of service disruptionnextguardhq.com · CVSS v3.1 Base Score
What do these metrics mean?
Attack Vector
Network — remotely exploitable over the internet. No physical or local access required. Widest attack surface.
Attack Complexity
Low — no special conditions required. Attacker can exploit reliably without depending on rare configurations or timing.
Privileges Required
High — admin or privileged account required to exploit.
User Interaction
None — attack is automatic and silent. Victim does nothing: no click, no file open.
Scope
Changed — successful attack can pivot beyond the vulnerable component to other systems or the host OS.
Confidentiality
High — complete confidentiality loss. Attacker can read all data: credentials, keys, personal data.
Integrity
High — attacker can write, modify, or delete any data: databases, config files, or code.
Availability
None — no availability impact. Service remains fully operational.

Affected Software

Componentbigip
VendorF5
Minimum version16.1.0
Maximum version21.0.0.2
Fixed in21.0.0.2

Weakness Classification (CWE)

Timeline

  1. Reserved
  2. Published

Mitigation and Workarounds

The primary mitigation for CVE-2026-32643 is to upgrade to F5 BIG-IP version 21.0.0.2 or later, which contains the fix. If immediate upgrade is not feasible, consider implementing stricter access controls for the Certificate Manager role, limiting its scope and duration. Review existing configurations for any unusual or unauthorized modifications. Implement network segmentation to limit the potential blast radius of a successful exploit. While a WAF or proxy cannot directly prevent this vulnerability, it can help detect and block suspicious command execution attempts. Monitor system logs for unusual activity related to configuration object modifications.

How to fix

Actualice a una versión corregida de BIG-IP o BIG-IQ. F5 ha publicado parches para solucionar esta vulnerabilidad. Consulte la documentación de F5 para obtener instrucciones detalladas sobre cómo aplicar las actualizaciones y mitigar el riesgo.

Frequently asked questions

What is CVE-2026-32643 — Privilege Escalation in F5 BIG-IP?

CVE-2026-32643 is a HIGH severity vulnerability affecting F5 BIG-IP and BIG-IQ systems. It allows an authenticated attacker with the Certificate Manager role to execute arbitrary commands, potentially leading to system compromise.

Am I affected by CVE-2026-32643 in F5 BIG-IP?

You are likely affected if you are running F5 BIG-IP or BIG-IQ versions between 16.1.0 and 21.0.0.2. Check your version and upgrade accordingly.

How do I fix CVE-2026-32643 in F5 BIG-IP?

Upgrade to F5 BIG-IP version 21.0.0.2 or later to remediate the vulnerability. If immediate upgrade is not possible, implement stricter access controls for the Certificate Manager role.

Is CVE-2026-32643 being actively exploited?

As of the current date, there are no publicly known active campaigns exploiting CVE-2026-32643, but the potential for exploitation remains.

Where can I find the official F5 advisory for CVE-2026-32643?

Refer to the official F5 security advisory for detailed information and mitigation guidance: [https://www.f5.com/security/center/advisory/f5-security-advisory-32643](https://www.f5.com/security/center/advisory/f5-security-advisory-32643)

Is your project affected?

Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.

livefree scan

Try it now — no account

Upload any manifest (composer.lock, package-lock.json, WordPress plugin list…) or paste your component list. You get a vulnerability report instantly. Uploading a file is just the start: with an account you get continuous monitoring, Slack/email alerts, multi-project and white-label reports.

Manual scanSlack/email alertsContinuous monitoringWhite-label reports

Drag & drop your dependency file

composer.lock, package-lock.json, requirements.txt, Gemfile.lock, pubspec.lock, Dockerfile...