CVE-2026-94127

validatedZero produced an exploit or a check.

EUVD-2026-84427 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+2.2dkevAttacks confirmed in the real world.+4h44m
f5 BIG-IP >= 21.1.0, < Hotfix-BIGIP-21.1.0.2.0.30.22-ENG; >= 17.5.0, < Hotfix-BIGIP-17.5.1.9.0.160.12-ENG; >= 17.1.0, < Hotfix-BIGIP-17.1.3.5.0.41.14-ENG
fixed in Hotfix-BIGIP-21.1.0.2.0.30.22-ENG, Hotfix-BIGIP-17.5.1.9.0.160.12-ENG, Hotfix-BIGIP-17.1.3.5.0.41.14-ENG
CWE-122 Heap-based Buffer Overflow
ETK-2026-199, permanent identifier
+9.4dTTV
11mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal −0.6dcve.org publicationkev+0.2dpublic poc+2.2dcheck available+9.4dagent stopped
+4d
+6d
+8d
+10d

description

BIG-IP deployments using APM as an OAuth Authorization Server with an access policy on a virtual server are affected. An unauthenticated remote attacker may execute code through the data plane; control-plane access is not implicated. Configurations used only as OAuth clients or resource servers are not affected.

mitigation

Install the applicable hotfix: 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. Until patched, remove or disable OAuth Authorization Server profiles from exposed APM virtual servers where operationally feasible.

fixed in Hotfix-BIGIP-21.1.0.2.0.30.22-ENG, Hotfix-BIGIP-17.5.1.9.0.160.12-ENG, Hotfix-BIGIP-17.1.3.5.0.41.14-ENG

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
2.2%82nd percentile
agent run time
11m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-22 14:17Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+2.2d
Δ to kevAttacks confirmed in the real world.
+4h44m

outcome

Contextual check: a technique exists and was validated, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-09-22
    euvd: trigger signal, started the run
  2. 2026-09-22 00:00Z
  3. 2026-09-22 00:00Z
  4. 2026-09-22 00:00Z
  5. 2026-09-22 14:17Z
  6. 2026-10-01 07:22Z
  7. 2026-10-02 05:49Z
    Critical FortiMail Zero-Day Flaw Exploited in Attacks Allows Unauthenticated Arbitrary File Writes

this entry in the feed

GET /api/v1/feed/CVE-2026-94127

{
  "etk_id": "ETK-2026-199",
  "cve_id": "CVE-2026-94127",
  "display_id": "CVE-2026-94127",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-84427",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated code execution in BIG-IP APM OAuth authorization",
  "summary": "BIG-IP deployments using APM as an OAuth Authorization Server with an access policy on a virtual server are affected. An unauthenticated remote attacker may execute code through the data plane; control-plane access is not implicated. Configurations used only as OAuth clients or resource servers are not affected.",
  "mitigation": "Install the applicable hotfix: 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. Until patched, remove or disable OAuth Authorization Server profiles from exposed APM virtual servers where operationally feasible.",
  "vendor": "f5",
  "product": "BIG-IP",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 21.1.0, < Hotfix-BIGIP-21.1.0.2.0.30.22-ENG",
        ">= 17.5.0, < Hotfix-BIGIP-17.5.1.9.0.160.12-ENG",
        ">= 17.1.0, < Hotfix-BIGIP-17.1.3.5.0.41.14-ENG"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "Hotfix-BIGIP-21.1.0.2.0.30.22-ENG",
        "Hotfix-BIGIP-17.5.1.9.0.160.12-ENG",
        "Hotfix-BIGIP-17.1.3.5.0.41.14-ENG"
      ],
      "package_name": "BIG-IP",
      "purl": null
    }
  ],
  "cwes": [
    122
  ],
  "cvss_score": 9.8,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0223,
  "epss_percentile": 0.8248,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 11.397169516666667,
  "t0_at": "2026-09-22T14:17:42.730000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-02T00:13:08.931903+00:00",
      "days": 9.413497707210649,
      "is_lower_bound": false,
      "measured_at": "2026-09-22T14:17:42.730000+00:00",
      "url": null
    },
    "kev": {
      "at": "2026-09-22T19:02:09.978800+00:00",
      "days": 0.19753760185185185,
      "is_lower_bound": false,
      "measured_at": "2026-09-22T14:17:42.730000+00:00",
      "precision": "exact",
      "url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?search_api_fulltext=CVE-2026-94127"
    },
    "public_poc": {
      "at": "2026-09-24T19:22:13+00:00",
      "days": 2.2114614583333334,
      "is_lower_bound": false,
      "measured_at": "2026-09-22T14:17:42.730000+00:00",
      "url": "https://github.com/watchtowrlabs/watchTowr-vs-f5-bigip-PreAuth-RCE-CVE-2026-94127"
    },
    "trigger_signal": {
      "at": "2026-09-22T00:00:00+00:00",
      "days": -0.5956334490740741,
      "is_lower_bound": false,
      "measured_at": "2026-09-22T14:17:42.730000+00:00",
      "url": "https://euvd.enisa.europa.eu/enisa/EUVD-2026-84427"
    }
  }
}

published 2026-10-01 03:29Z
last change 2026-10-21 06:02Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.