F5 BIG-IP APM Hotfixes Address Critical OAuth Vulnerability

P1 — VALIDATE AND UPDATECritical · 9.8 (CVSS v3.1) / 9.3 (CVSS v4.0)EXPLOITATION: NOT STATED

Quick Answer

The authority published K000162605 for BIG-IP APM 21.1, 17.5, and 17.1 virtual servers configured with an APM access policy and OAuth profile. F5 states that a specifically crafted OAuth request against an APM access policy and OAuth profile can compromise confidentiality, integrity, and availability without authentication. Affected deployments should be matched to the authority's exact scope and moved to the supported fixed release.

Confirm Scope And Apply The Supported Fix

What to do now: Inventory BIG-IP APM 21.1, 17.5, and 17.1 virtual servers configured with an APM access policy and OAuth profile, match the exact affected release or feature, apply the authority-supported fixed build or service remediation, validate the dependent workflow, and preserve evidence.

Open the authoritative advisory

Last verified: 2026-09-22 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeBIG-IP APM 21.1, 17.5, and 17.1 virtual servers configured with an APM access policy and OAuth profile
AdvisoryK000162605
CVECVE-2026-94127
Authoritative release date2026-09-22 14:17:42.730 UTC
Authority revision date2026-09-22 14:17:42.730 UTC
Affected versionsBIG-IP 21.1.0 before Hotfix-BIGIP-21.1.0.2.0.30.22-ENG, 17.5.x before Hotfix-BIGIP-17.5.1.9.0.160.12-ENG, and 17.1.x before Hotfix-BIGIP-17.1.3.5.0.41.14-ENG, when the advisory configuration is present.
Fixed versionHotfix-BIGIP-21.1.0.2.0.30.22-ENG, Hotfix-BIGIP-17.5.1.9.0.160.12-ENG, or Hotfix-BIGIP-17.1.3.5.0.41.14-ENG as appropriate
CVSS base score9.8 (CVSS v3.1) / 9.3 (CVSS v4.0)
CVSS severityCritical
Exploitation statusNot stated by the authority; no exploitation claim is inferred.

What Changed

F5 states that a specifically crafted OAuth request against an APM access policy and OAuth profile can compromise confidentiality, integrity, and availability without authentication.

What To Validate Now

  1. Inventory. Locate BIG-IP APM 21.1, 17.5, and 17.1 virtual servers configured with an APM access policy and OAuth profile deployments, versions, enabled features, exposure paths, owners, and dependent services.
  2. Establish applicability. Compare each deployment with the authority's affected-version statement: BIG-IP 21.1.0 before Hotfix-BIGIP-21.1.0.2.0.30.22-ENG, 17.5.x before Hotfix-BIGIP-17.5.1.9.0.160.12-ENG, and 17.1.x before Hotfix-BIGIP-17.1.3.5.0.41.14-ENG, when the advisory configuration is present. Do not infer applicability from product family or severity alone.
  3. Remediate. Apply Hotfix-BIGIP-21.1.0.2.0.30.22-ENG, Hotfix-BIGIP-17.5.1.9.0.160.12-ENG, or Hotfix-BIGIP-17.1.3.5.0.41.14-ENG as appropriate through the supported vendor or project channel, following the current advisory and change-control requirements.
  4. Validate. Confirm the resulting version or managed-service state, exercise representative functionality and recovery paths, monitor for regressions, and document exceptions.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Use the exact supported release stream and repository. Test dependencies, clusters, integrations, and rollback before broad deployment; a CVSS rating or reachable feature is not evidence of exploitation.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.