Skip to main content
Menu
CVEs

CVE

F5 BIG-IP denial of service in TMM SAML service provider handling

CVE-2026-126822EUVD-2026-128960GHSA-64W6-C5J7-P636Published Updated

7.5HighCNA
Exploited
No known exploitation
Fix
Fixed in BIGIP-21.1.0.4.0.19.3-ENG, BIGIP-17.5.1.11.0.61.12-ENG, BIGIP-17.1.3.7.0.21.4-ENG
Who is exposed
Not reported

Do first: Upgrade to a fixed version: BIGIP-21.1.0.4.0.19.3-ENG, BIGIP-17.5.1.11.0.61.12-ENG, BIGIP-17.1.3.7.0.21.4-ENG.

Summary

Description:

When BIG-IP APM is provisioned, an Access Profile is configured as a SAML SP (Service Provider) and is applied to a virtual server, undisclosed requests can cause the Traffic Management Microkernel (TMM) to terminate.

Impact:

Traffic is disrupted while the TMM process restarts. This vulnerability allows a remote unauthenticated attacker to cause a denial-of-service (DoS) on the BIG-IP system.

There is no control plane exposure; this is a data plane issue only.

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

cve.now Index

28Pcve.now Index 28 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.5/10CVSS 7.5
  • No patch0/5No signal

What would change the score

  • Would score about 73 if added to CISA KEV
  • Would score about 68 if CISA's SSVC rates exploitation active
  • Would score about 33 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: BIGIP-21.1.0.4.0.19.3-ENG, BIGIP-17.5.1.11.0.61.12-ENG, BIGIP-17.1.3.7.0.21.4-ENG.

  • Workaround: Restrict network access to the virtual server hosting the SAML SP to trusted client networks.

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-126822 (BIG-IP APM SAML 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-126822 (entry last updated 2026-11-18):
Affected:
- F5 BIG-IP: from 21.1.0, fixed in BIGIP-21.1.0.4.0.19.3-ENG; from 17.5.0, fixed in BIGIP-17.5.1.11.0.61.12-ENG; from 17.1.0, fixed in BIGIP-17.1.3.7.0.21.4-ENG
Fixed versions: BIGIP-21.1.0.4.0.19.3-ENG, BIGIP-17.5.1.11.0.61.12-ENG, BIGIP-17.1.3.7.0.21.4-ENG.
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: Restrict network access to the virtual server hosting the SAML SP to trusted client networks. (source: https://www.cve.org/CVERecord?id=CVE-2026-126822)
CISA KEV: CVE-2026-126822 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126822 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/K000163942
- https://www.cve.org/CVERecord?id=CVE-2026-126822
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-126822
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-126822"}.

Timeline

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

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Affected versions

  • F5 BIG-IP

    From 21.1.0 · fixed in BIGIP-21.1.0.4.0.19.3-ENG; From 17.5.0 · fixed in BIGIP-17.5.1.11.0.61.12-ENG; From 17.1.0 · fixed in BIGIP-17.1.3.7.0.21.4-ENG

Evidence 3

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

Corrections

None so far.

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

Questions about CVE-2026-126822

Is CVE-2026-126822 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-126822?

BIG-IP: from 21.1.0 before BIGIP-21.1.0.4.0.19.3-ENG; from 17.5.0 before BIGIP-17.5.1.11.0.61.12-ENG; from 17.1.0 before BIGIP-17.1.3.7.0.21.4-ENG.Source: cve.now feed data

How do I fix CVE-2026-126822?

Upgrade to a fixed build: BIGIP-21.1.0.4.0.19.3-ENG, BIGIP-17.5.1.11.0.61.12-ENG, or BIGIP-17.1.3.7.0.21.4-ENG, matching your release line. If you cannot upgrade yet, see the workaround for the SAML service provider virtual server.Source: cve.org

More CVEs