purocean Yank Note 3.93.0 Settings Endpoint src/main/server/index.ts config.getAll information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 1.38+ |
Summary
A vulnerability marked as problematic has been reported in purocean Yank Note 3.93.0. Affected is the function config.getAll of the file src/main/server/index.ts of the component Settings Endpoint. This manipulation causes information disclosure.
This vulnerability is registered as CVE-2026-122154. Remote exploitation of the attack is possible. Furthermore, an exploit is available.
It is suggested to upgrade the affected component.
The commit removes the key from the response.
Details
A vulnerability classified as problematic was found in purocean Yank Note 3.93.0. Affected by this vulnerability is the function config.getAll of the file src/main/server/index.ts of the component Settings Endpoint. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality.
It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-122154. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
It is possible to download the exploit at github.com. It is declared as proof-of-concept. The commit removes the key from the response.
Upgrading to version 3.93.1 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 59f85d48f17a70a402ad59dcecacdbec20f954df 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.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔒
VulDB Reliability: 🔍
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
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: Yank Note 3.93.1
Patch: 59f85d48f17a70a402ad59dcecacdbec20f954df
Timeline
11/04/2026 Advisory disclosed11/04/2026 VulDB entry created
11/04/2026 VulDB entry last update
Sources
Advisory: 532Status: Confirmed
Confirmation: 🔒
CNA: VulDB
CVE: CVE-2026-122154 (🔒)
GCVE (CVE): GCVE-0-2026-122154
GCVE (VulDB): GCVE-100-431155
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 11/04/2026 19:40Changes: 11/04/2026 19:40 (64)
Complete: 🔍
Submitter: CopperKoi
Cache ID: 216::103
Submit
Accepted
- Submit #1028031: Purocean Yank Note 3.93.0 Information Disclosure (by CopperKoi)
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.