CVE-2026-35467 | CERTCC cveClient up to 1.1.14 Stored API encrypt-storage.js insufficiently protected credentials

VDB-355038 · CVE-2026-35467 · EUVD-2026-18554 CERTCC CVECLIENT UP TO 1.1.14 STORED API ENCRYPT-STORAGE.JS INSUFFICIENTLY PROTECTED CREDENTIALS HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 2.5 $0-$5k 0.87+ Summaryinfo A vulnerability described as problematic has been identified in CERTCC cveClient up to 1.1.14. This affects an unknown part of the file encrypt-storage.js of the component Stored API. The manipulation results in insufficiently protected credentials. This vulnerability was named CVE-2026-35467. The attack may be performed from remote. There is no available exploit. Upgrading the affected component is recommended. Detailsinfo A vulnerability was found in CERTCC cveClient up to 1.1.14. It has been classified as problematic. Affected is an unknown code block of the file encrypt-storage.js of the component Stored API. The manipulation with an unknown input leads to a insufficiently protected credentials vulnerability. CWE is classifying the issue as CWE-522. The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. This is going to have an impact on confidentiality. CVE summarizes: The stored API keys in temporary browser client is not marked as protected allowing for JavScript console or other errors to allow for extraction of the encryption credentials. The weakness was presented by Jerry Gamblin. The advisory is available at github.com. This vulnerability is traded as CVE-2026-35467 since 04/02/2026. The exploitability is told to be difficult. It is possible to launch the attack remotely. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1552 by the MITRE ATT&CK project. Upgrading to version 1.1.15 eliminates this vulnerability. Applying a patch 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. The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-18554). Productinfo Vendor CERTCC Name cveClient Version 1.1.0 1.1.1 1.1.2 1.1.3 1.1.4 1.1.5 1.1.6 1.1.7 1.1.8 1.1.9 1.1.10 1.1.11 1.1.12 1.1.13 1.1.14 Website Product: https://github.com/CERTCC/cveClient/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 2.6 VulDB Meta Temp Score: 2.5 VulDB Base Score: 2.6 VulDB Temp Score: 2.5 VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv2info 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: 🔍 Exploitinginfo Class: Insufficiently protected credentials CWE: CWE-522 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 Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: cveClient 1.1.15 Patch: github.com Timelineinfo 04/02/2026 CVE reserved 04/02/2026 +0 days VulDB entry created 04/03/2026 +0 days Advisory disclosed 04/03/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: github.com Researcher: Jerry Gamblin Status: Confirmed CVE: CVE-2026-35467 (🔒) GCVE (CVE): GCVE-0-2026-35467 GCVE (VulDB): GCVE-100-355038 EUVD: 🔒 Entryinfo Created: 04/03/2026 00:09 Updated: 04/03/2026 01:54 Changes: 04/03/2026 00:09 (57), 04/03/2026 01:54 (1) Complete: 🔍 Cache ID: 99:6FA:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸