WatchGuard AuthPoint Gateway Improper HMAC Validation in LDAP Authentication Callback Allows Forged Authentication Results
Affects WatchGuard AuthPoint Authentication Gateway from 1.0 up to but not including 7.6.0 when configured with an LDAP provider. Fixed in 7.6.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 7.6.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 7.6.0.
- Exploitation0/40No signal
- Exposure17/25No login or user action needed, reachable over the network without a login · Data gap: Advisories don't say whether default setups are affected
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity8.9/10CVSS 8.9
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
CVE-2026-121637 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.9 (high) and affects AuthPoint Authentication Gateway; fixed in 7.6.0.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 7.6.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
WatchGuard AuthPoint Gateway is affected by a flaw in its LDAP authentication callback that lets a network attacker who has obtained a valid header signature forge authentication results and transaction identifiers, leading to unauthorized session outcomes. The attack can be carried out remotely, without logging in and without any user action.
Read the original description
An improper integrity validation vulnerability in WatchGuard AuthPoint Gateway's LDAP authentication callback allows a network attacker who has obtained a valid header signature to forge the authentication result and transaction identifier in the request body, resulting in unauthorized session outcomes.
What to do
Upgrade to a fixed version: 7.6.0.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- WatchGuard AuthPoint Authentication Gateway
From 1.0 · fixed in 7.6.0
Evidence 1
- Advisory
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121637
Is CVE-2026-121637 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The HMAC validation in the LDAP authentication callback is improperly implemented. A network attacker who has obtained a valid header signature can forge the authentication result and transaction identifier in the request body, which can produce unauthorized session outcomes.Source: psirt.watchguard.com
Which versions are affected by CVE-2026-121637?
AuthPoint Authentication Gateway: from 1.0 before 7.6.0.Source: cve.now feed data
Am I affected, and how do I check?
Versions from 1.0 up to but not including 7.6.0 of the AuthPoint Authentication Gateway are affected, but only deployments configured with an LDAP provider. Installed version and whether an LDAP provider is configured in the gateway settings are the two things to check.Source: psirt.watchguard.com
How do I fix CVE-2026-121637?
Upgrade the AuthPoint Authentication Gateway to version 7.6.0 or later, which is the fixed release named by WatchGuard. No workaround is listed in the available facts.Source: psirt.watchguard.com