Quick answers
- Is CVE-2026-121638 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-121638 being exploited in the wild.
- How severe is CVE-2026-121638?
- Informational severity, published 4 November 2026.
- Which products and versions are affected?
- Watchguard AuthPoint Authentication Gateway < 7.6.0.
- Is there a fix for CVE-2026-121638?
- Yes: fixed in AuthPoint Authentication Gateway 7.6.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-121638 attacked?
- It is attacked over the network or from the adjacent network, in a hosted service.
- Am I affected by CVE-2026-121638?
- Check whether you run Watchguard AuthPoint Authentication Gateway at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: AuthPoint Authentication Gateway 7.6.0
Technical details
The vulnerability stems from improper certificate validation (CWE-295) in the AuthPoint Gateway's communication with RADIUS, LDAP, or ADFS authentication providers. An attacker with an on-path network position can perform a man-in-the-middle attack to intercept and modify communications. The vulnerability affects versions before 7.6.0 only when the gateway is configured to use one of these authentication resources.
Affected products
- WatchGuard AuthPoint Authentication Gateway < 7.6.0
Timeline
- 2026-11-04: disclosed
- 2026-11-04: advisory