Quick answers
- Is CVE-2026-110653 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-110653 being exploited in the wild.
- How severe is CVE-2026-110653?
- Critical severity, with a CVSS score of 9.1, published 17 October 2026.
- Which products and versions are affected?
- LatePoint up to and including 5.7.4.
- Is there a fix for CVE-2026-110653?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-110653 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-110653?
- Check whether you run LatePoint 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.
Technical details
The vulnerability is a TOCTOU race condition in the verifyOTP function where the OTP attempt counter is incremented using a stale in-memory value without atomic transactions or row-level locking. An unauthenticated attacker can fire concurrent requests to the auth__verify_otp endpoint to bypass the 10-attempt lockout, brute-force the OTP code, and authenticate as any customer whose email or phone is known. The publicly obtainable nonce from unauthenticated endpoints does not provide protection.
Affected products
- LatePoint LatePoint up to and including 5.7.4
Timeline
- 2026-10-17: disclosed