BlackTree Security · Infrastructure · Automation · AI

BIG-IP APM’s OAuth Server Role Opens an Exploited Code Execution Path

The product guarding access to the network may now be the way into it.

F5 has confirmed active exploitation of CVE-2026-94127, a critical heap-based buffer overflow in BIG-IP Access Policy Manager. Under the affected configuration, an unauthenticated remote attacker can reach privileged functionality and execute code on the appliance.

The vulnerability is rated 9.8 under CVSS 3.1 and 9.3 under CVSS 4.0. F5 lists BIG-IP APM 17.1.0 through 17.1.3, 17.5.0 through 17.5.1 and 21.1.0 as affected, subject to the specific OAuth role and virtual-server configuration.

The configuration needs the OAuth authorisation-server role, with both the access policy and OAuth profile attached to the virtual server. Deployments using APM strictly as an OAuth Client or Resource Server, without authorisation-server profiles configured, are not affected through this path. Do not infer exposure from the product name or the presence of OAuth alone. Treat internet-facing matches as potential incident-response cases rather than ordinary patch tickets.

Appliance mode does not remove the vulnerability. F5 identifies this as a data-plane issue with no control-plane exposure. Restricting the management interface is useful defence in depth, but it does not remediate malicious traffic reaching the affected application virtual server.

Update, 31 October 2026: The current vendor advisory, marked revised on 15 October, lists ordinary fixed releases as well as engineering-hotfix alternatives. Match the exact installed build, branch and affected configuration; the two formats below describe different release identifiers.

APM branch Listed vulnerable ordinary releases Ordinary fix starts at
17.1 17.1.0 through 17.1.3 17.1.3.6
17.5 17.5.0 through 17.5.1 17.5.1.10
21.1 21.1.0 21.1.0.3
Use the vendor’s full build and configuration guidance, rather than the branch number alone.

The official F5-authored CVE record expresses the affected ranges using these engineering-hotfix boundaries:

  • 17.1: starts at 17.1.0 and stops before Hotfix-BIGIP-17.1.3.5.0.41.14-ENG.
  • 17.5: starts at 17.5.0 and stops before Hotfix-BIGIP-17.5.1.9.0.160.12-ENG.
  • 21.1: starts at 21.1.0 and stops before Hotfix-BIGIP-21.1.0.2.0.30.22-ENG.

F5 retains those engineering hotfixes as alternatives in its remediation table and says they contain the fixes in its Hardened Releases 2 set. Follow the actual vendor download and deployment instructions rather than constructing a filename from a version label. The advisory says a fix also applies to later minor, maintenance and point releases within that same branch. Software beyond End of Technical Support was not evaluated, so an unlisted old version is not evidence of safety.

Preserve evidence while arranging remediation

CERT-EU recommends preserving forensic evidence, applying the relevant hotfix and conducting a compromise assessment. That order is important. An appliance reboot, rushed cleanup or incomplete log collection can remove the evidence needed to establish whether exploitation preceded remediation.

F5’s published detection guidance centres on a sequence rather than a single unmistakable indicator: repeated OAuth authentication failures, suspicious commands in the audit trail and a TMM process failure or core file close together in time.

  • Review /var/log/apm for repeated invalid-token failures. F5 describes sustained repetition of ten or more in one log, particularly from one source address; CERT-EU adds the short-window emphasis. A single invalid-token message can occur normally and does not confirm compromise.
  • Use tmctl global_oauth_stat -s total_requests,total_userinfo_requests,total_failed to look for an unexplained rise in failed OAuth requests.
  • Correlate those events with suspicious commands in /var/log/audit.
  • Investigate unexpected TMM SIGABRT events, loops and core files. F5 describes loops followed by the SOD daemon sending SIGABRT. A core file alone is not proof of exploitation; correlate it with the authentication and audit sequence.
  • Preserve relevant logs, core files, configuration and timestamps before remediation where operationally possible.

If patching cannot happen immediately, F5 can provide an iRule-based mitigation through its support channel. That is a bridge, not a substitute for the hotfix and compromise assessment.

The gateway problem is bigger than the vulnerability score

Access gateways sit where identity, remote access and internal applications meet. They are designed to see and control traffic that most other systems never touch. Successful code execution there can therefore create a path towards credentials, sessions, application traffic and the wider network.

BlackTree previously covered a different BIG-IP APM flaw that could support a memory-only web shell. The new issue is not a continuation of that CVE and should not be conflated with it. The recurring lesson is architectural: perimeter appliances are not just controls. They are high-value computers with privileged placement and their own incident-response requirements.

What teams should do now

  • Inventory the relevant configuration. Find BIG-IP APM virtual servers with both an access policy and OAuth profile in the authorisation-server role. Record the full running build and distinguish Client or Resource Server-only deployments.
  • Prioritise exposed systems. Internet-facing matches deserve immediate attention, but do not ignore reachable internal application virtual servers using the affected data-plane configuration.
  • Capture evidence first. Export logs and relevant forensic artefacts before changes erase the timeline.
  • Apply the hotfix. Follow F5’s version-specific guidance and validate the resulting build.
  • Hunt beyond the appliance. If exploitation is suspected, investigate credentials, sessions and systems accessible through the gateway.
  • Restrict management and monitoring paths. Reduce unnecessary exposure and make appliance telemetry part of central detection. Management restrictions do not replace the fix or mitigation on the affected virtual server.

The difference between patch management and incident response is evidence of exploitation. F5 has already supplied that evidence at the campaign level. Affected organisations now need to determine whether it also exists in their own logs.

Sources

Leave a Reply

Your email address will not be published. Required fields are marked *