Cap-go up to 12.128.1 Device Identifier access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 3.39+ |
Summary
A vulnerability, which was classified as critical, was found in Cap-go up to 12.128.1. The impacted element is an unknown function of the component Device Identifier Handler. Such manipulation leads to access control. This vulnerability is uniquely identified as CVE-2026-53982. The attack can be launched remotely. No exploit exists. You should upgrade the affected component.
Details
A vulnerability was found in Cap-go up to 12.128.1 and classified as critical. Affected by this issue is some unknown functionality of the component Device Identifier Handler. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is availability. CVE summarizes:
Capgo Console prior to 12.28.2 contains a denial-of-service vulnerability in its account deletion flow that allows an attacker to block authentication and onboarding functions by triggering account deletion while a device identifier is linked to the active session. The platform incorrectly associates the deletion state with the device identifier, causing the affected device or browser environment to be redirected to an account-disabled page for approximately 30 days, preventing any account login or registration from that device.
The weakness was disclosed by Naitik Gupta as GHSA-qmrm-qgwr-55jf. The advisory is shared for download at github.com. This vulnerability is handled as CVE-2026-53982 since 06/11/2026. The exploitation is known to be easy. The attack may be launched remotely. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1068.
Upgrading to version 12.128.2 eliminates this vulnerability. Applying the patch 6685e5f11adef257bf3d085e481f4d8ebcec602e is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.5
CNA Vector (VulnCheck): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Access controlCWE: CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Cap-go 12.128.2
Patch: 6685e5f11adef257bf3d085e481f4d8ebcec602e
Timeline
06/11/2026 CVE reserved06/12/2026 Advisory disclosed
06/12/2026 VulDB entry created
06/12/2026 VulDB entry last update
Sources
Advisory: GHSA-qmrm-qgwr-55jfResearcher: Naitik Gupta
Status: Confirmed
CVE: CVE-2026-53982 (🔒)
GCVE (CVE): GCVE-0-2026-53982
GCVE (VulDB): GCVE-100-370652
Entry
Created: 06/12/2026 19:35Changes: 06/12/2026 19:35 (79)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.