Skip to main content
Menu
CVEs

CVE

F5 BIG-IP token expiry bypass in iControl REST

CVE-2026-120718EUVD-2026-128940Published Updated Summary written by a model

8.1HighCNA
Exploited
No known exploitation
Fix
Fixed in BIG-IP 21.1.0.2, 17.5.1.10, 17.1.3.6 · BIG-IQ 8.4.2.3
Who is exposed
Not reported

Do first: Upgrade to a fixed version: BIG-IP 21.1.0.2, 17.5.1.10, 17.1.3.6 · BIG-IQ 8.4.2.3.

Summary

F5 BIG-IP and BIG-IQ are affected by a flaw in the iControl REST interface, where tokens may not expire as expected. An attacker who has already obtained a token can extend its lifetime remotely, without logging in, unless the token owner deletes it.

Original description

Description: BIG-IP iControl REST tokens may not expire as expected in all scenarios.

Impact: An attacker who has obtained a token may be able to extend its expiry lifetime unless the token owner deletes it. There is no data plane exposure; this is a control plane issue only.

Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

cve.now Index

26Pcve.now Index 26 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.1/10CVSS 8.1, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 71 if added to CISA KEV
  • Would score about 66 if CISA's SSVC rates exploitation active
  • Would score about 31 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: BIG-IP 21.1.0.2, 17.5.1.10, 17.1.3.6 · BIG-IQ 8.4.2.3.

  • Workaround: Modify scripts that create REST tokens to delete them at the end of their useful life.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-120718 (BIG-IP iControl REST Vulnerability), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-120718 (entry last updated 2026-11-18):
Affected:
- F5 BIG-IP: from 21.1.0, fixed in 21.1.0.2; from 17.5.0, fixed in 17.5.1.10; from 17.1.0, fixed in 17.1.3.6
- F5 BIG-IQ: from 8.4.0, fixed in 8.4.2.3
Fixed versions: 21.1.0.2, 17.5.1.10, 17.1.3.6, 8.4.2.3.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
Workaround: Modify scripts that create REST tokens to delete them at the end of their useful life. (source: https://www.cve.org/CVERecord?id=CVE-2026-120718)
CISA KEV: CVE-2026-120718 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-120718 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://my.f5.com/manage/s/article/K000163929
- https://www.cve.org/CVERecord?id=CVE-2026-120718
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-120718
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-120718"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Affected versions

  • F5 BIG-IP

    From 21.1.0 · fixed in 21.1.0.2; From 17.5.0 · fixed in 17.5.1.10; From 17.1.0 · fixed in 17.1.3.6

  • F5 BIG-IQ

    From 8.4.0 · fixed in 8.4.2.3

Evidence 3

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-120718
RecordNVD · CVE-2026-120718
Other links 1
Patchmy.f5.com · manage/s/article/K000163929

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-120718

Is CVE-2026-120718 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-120718?

BIG-IP: from 21.1.0 before 21.1.0.2; from 17.5.0 before 17.5.1.10; from 17.1.0 before 17.1.3.6. BIG-IQ: from 8.4.0 before 8.4.2.3.Source: cve.now feed data

How do I fix CVE-2026-120718?

Upgrade BIG-IP to 21.1.0.2, 17.5.1.10, or 17.1.3.6, or BIG-IQ to 8.4.2.3, matching your release line. The facts give no other patch ids, and the only workaround named is to modify scripts that create REST tokens so they delete them at the end of their useful life.Source: cve.org

More CVEs