Skip to main content
VulnerabilityPublished

CVE-2026-121637: WatchGuard AuthPoint Authentication Gateway · Insufficient Verification of Data Authenticity

Affects WatchGuard AuthPoint Authentication GatewaySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.9 High : upgrade to 7.6.0 soon.

Data as of 4 Nov 2026, 15:13 UTC

CVSS 4.0 base score
8.9High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (WatchGuard)CVSS 4.08.9
Patch
Available – fixed in 7.6.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

What to do

Upgrade WatchGuard AuthPoint Authentication Gateway to 7.6.0.

Affected software

ProductAffectedFixed in
WatchGuardAuthPoint Authentication GatewayAffected
  • >=1.0 <7.6.0
Fixed in
  • 7.6.0

AI-suggested

Upgrade WatchGuard AuthPoint Authentication Gateway to version 7.6.0 or later, where this vulnerability is fixed. No other mitigation steps are indicated by the vendor advisory.

Description

CVE-2026-121637 is a high-severity vulnerability in WatchGuard AuthPoint Authentication Gateway versions 1.0 up to but not including 7.6.0. It involves improper integrity validation of LDAP authentication callback data, allowing an attacker with a valid header signature to forge authentication results and transaction identifiers, potentially causing unauthorized session outcomes. The issue is fixed in version 7.6.0.

References

Community reviews

Loading reviews…