External risk intelligence

BIG-IP iControl REST Token Expiry Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.2)

CVE-2026-120718

The vulnerability affects the BIG-IP iControl REST interface. F5 BIG-IP devices are commonly deployed as internet-facing application delivery controllers, gateways, and load balancers. Management and API interfaces on these appliances are frequently exposed to the network to facilitate remote administration and integration, making them a common target for internet-based reachability.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This CVE addresses a concern where tokens on BIG-IP iControl REST may not expire as expected, potentially allowing an attacker who has already obtained a token to extend its validity unless explicitly deleted. This issue is limited to the control plane, meaning there is no direct exposure of user data. The primary concern at this stage is to confirm if this specific technology is in use and if it presents any exposure.

  • Tokens might not expire, extending access.
  • Affects critical control plane functions.
  • Confirm relevance and any exposure.

Attack Path

How an attacker could exploit the issue

An attacker who has obtained a token could potentially extend its lifespan, granting them prolonged access to the control plane. This issue affects the BIG-IP iControl REST interface, which is often exposed externally for management purposes.

  • Entry condition: Attacker obtains a token.
  • Trigger point: Token expiry lifetime is extended.
  • Resulting risk: Prolonged control plane access.

Live Threat

Current exploitation, exposure, and threat context

BIG-IP iControl REST tokens may have extended expiry lifetimes if an attacker obtains a token and the token owner does not delete it, affecting control plane operations.

  • Control plane token expiration.
  • Extended token lifetime when obtained.
  • Unauthorized control plane access.

Operational Fix

Recommended remediation, mitigation, and detection steps

This control plane vulnerability in BIG-IP iControl REST affects the ability to manage the system and could allow an attacker with a token to extend its lifespan. Owners of BIG-IP systems must first confirm the scope of affected devices and their reachability from the network. Planning for remediation should consider the business criticality of each instance, as the impact is limited to the control plane.

  • Ownership rests with BIG-IP system administrators.
  • Verify BIG-IP iControl REST token expiry behavior.
  • Plan token owner-driven remediation actions.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is BIG-IP iControl REST?

BIG-IP iControl REST is an API interface for F5 BIG-IP appliances. It allows administrators and automated systems to programmatically manage, configure, and monitor the device's control plane. These appliances act as application delivery controllers, gateways, and load balancers, often sitting at the edge of a network to manage traffic.

What is the vulnerability in CVE-2026-120718?

This vulnerability relates to how the system manages authentication tokens. Under certain conditions, these tokens may fail to expire as intended. If an attacker manages to obtain a valid token, they could potentially extend its lifespan indefinitely, maintaining access to the control plane until the token is explicitly deleted by the owner.

How can an attacker trigger this issue?

The core requirement is that an attacker must first obtain a valid authentication token. Once they possess one, the vulnerability allows them to extend the token's validity period. Simply interacting with the API without an existing token does not trigger this specific expiry bug.

Why should I care about this if my device is internal?

Halo Surface Signal notes that BIG-IP devices are frequently internet-facing to support remote administration. While an internal device has a smaller attack surface, the risk remains if an attacker gains access to your internal network. You should prioritize assessing any instances where the iControl REST interface is reachable.

How do I respond to this threat?

Start by identifying all BIG-IP systems in your environment that utilize the iControl REST interface. Once mapped, verify the current token management practices for those devices. Coordinate with your system administrators to monitor for unauthorized token activity and plan for necessary updates to ensure tokens expire according to security policy.

References