Quick answers
- Is CVE-2026-56305 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-56305 being exploited in the wild.
- How severe is CVE-2026-56305?
- High severity, with a CVSS score of 8.3, published 10 July 2026.
- Which products and versions are affected?
- Capgo < 12.128.2.
- Is there a fix for CVE-2026-56305?
- 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-56305 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-56305?
- Check whether you run Capgo 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
An authentication bypass vulnerability exists in Capgo's password change endpoint due to a lack of current password validation (CWE-620). The backend fails to enforce a requirement for the existing password before accepting a new one, relying solely on the presence of an active session token. A remote attacker who has obtained a valid session—via session hijacking, XSS, or shared device access—can submit a password change request to the console settings. This results in a full account takeover and permanent lockout of the original user. The issue is resolved in version 12.128.2, which implements mandatory server-side validation of the current password.
Affected products
- Capgo Capgo < 12.128.2
Timeline
- 2026-02-10: advisory: Initial GHSA advisory published
- 2026-07-10: disclosed: CVE published to NVD