CVE-2026-121639

validatingZero is analyzing and reversing it now.

GHSA-836c-pvq3-wxwg ↗EUVD-2026-116932 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
WatchGuard AuthPoint Authentication Gateway >= 1.0, < 7.6.0
fixed in 7.6.0
CWE-252 Unchecked Return Value
ETK-2026-3509Zero's internal tracking ID, independent of the CVE number., permanent identifier
27mrunning
patch analysiscurrent stage
timeline
0 = trigger signal
trigger signal (cve.org) +0mvalidating
0
+30min
+60min
+90min

description

AuthPoint Authentication Gateway releases before 7.6.0 are affected by an authentication-control weakness. An unauthenticated remote attacker who can connect to the gateway host may disrupt authentication activity and erase the local directory synchronization configuration.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Upgrade AuthPoint Authentication Gateway to version 7.6.0 or later. Restrict network access to gateway hosts to trusted systems until the upgrade is complete.

fixed in 7.6.0

check
building now
exploit
not yet
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.
–
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.
–
agent run time
27m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-04 14:44Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Run in progress: no artifact yet.

source signals

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

  1. 2026-11-04 14:44Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3509",
  "cve_id": "CVE-2026-121639",
  "display_id": "CVE-2026-121639",
  "ghsa_id": "GHSA-836c-pvq3-wxwg",
  "euvd_id": "EUVD-2026-116932",
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Missing authentication in AuthPoint Authentication Gateway",
  "summary": "AuthPoint Authentication Gateway releases before 7.6.0 are affected by an authentication-control weakness. An unauthenticated remote attacker who can connect to the gateway host may disrupt authentication activity and erase the local directory synchronization configuration.",
  "mitigation": "Upgrade AuthPoint Authentication Gateway to version 7.6.0 or later. Restrict network access to gateway hosts to trusted systems until the upgrade is complete.",
  "vendor": "WatchGuard",
  "product": "AuthPoint Authentication Gateway",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.0, < 7.6.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "7.6.0"
      ],
      "package_name": "AuthPoint Authentication Gateway",
      "purl": null
    }
  ],
  "cwes": [
    252
  ],
  "cvss_score": 9.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 10.7768198,
  "t0_at": "2026-11-04T14:44:14.573000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-04T14:44:14.573000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-04T14:44:14.573000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-121639"
    }
  }
}

published 2026-11-04 14:56Z
last change 2026-11-04 16:21Z

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.