Bug ID 2225165: [APM] TMM crash using OAuth in API protection profile

Last Modified: Sep 29, 2026

Affected Product(s):
BIG-IP APM(all modules)

Known Affected Versions:
17.5.1, 17.5.1.2, 17.5.1.3, 17.5.1.4, 17.5.1.5, 17.5.1.6, 17.5.1.8, 17.5.1.9

Opened: Feb 17, 2026

Severity: 2-Critical

Symptoms

When an API protection profile uses OAuth to process or verify JWT tokens, TMM may terminate unexpectedly and generate a core file. The following messages may be logged: Access encountered error: ERR_NOT_FOUND OAuth Scope: failed ... Internal error during signature verification didn't find agent AccessV2 agent execution error 5 The issue may also result in API protection requests failing during JWT signature verification

Impact

Traffic is disrupted while tmm restarts. This can cause API protection authentication or authorization failures. Repeated occurrences may result in service disruption

Conditions

- BIG-IP APM is configured with an API protection profile - OAuth is used for JWT processing or verification - A crypto request remains in flight while the associated OAuth crypto context is replaced or released

Workaround

None

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips