CVE-2026-122154
Deferred Deferred - Pending Action

Information Disclosure in Yank Note

Publication date: 2026-11-05

Last updated on: 2026-11-05

Assigner: VulDB

Description
A vulnerability was found in purocean Yank Note 3.93.0. This impacts the function config.getAll of the file src/main/server/index.ts of the component Settings Endpoint. The manipulation results in information disclosure. The attack may be launched remotely. The exploit has been made public and could be used. Upgrading to version 3.93.1 will fix this issue. The patch is identified as 59f85d48f17a70a402ad59dcecacdbec20f954df. The affected component should be upgraded. The commit removes the key from the response.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-05
Last Modified
2026-11-05
Generated
2026-11-05
AI Q&A
2026-11-05
EPSS Evaluated
N/A
NVD
CVE-2026-122154
EUVD
EUVD-2026-117208

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
purocean Yank Note 3.93.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-200 The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
CWE-284 The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in purocean Yank Note 3.93.0 allows unauthenticated remote attackers to access the JWT signing key via an exposed settings endpoint. The flaw occurs because the `/api/settings` endpoint returns sensitive configuration data, including the plaintext JWT secret, without requiring authentication. Attackers can then forge admin tokens to gain elevated privileges.

Detection Guidance

Check if Yank Note v3.93.0 is running by inspecting processes or listening ports. Test for unauthenticated access to /api/settings endpoint using curl: curl http://localhost:3044/api/settings. If the response includes server.jwt-secret, the system is vulnerable.

Impact Analysis

An attacker exploiting this flaw could forge admin tokens to access all admin APIs, execute arbitrary JavaScript via `POST /api/rpc`, and perform remote code execution. The JWT secret remains on disk, so a single breach compromises the installation until the data directory is reset.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating GDPR's data protection principles and HIPAA's security requirements for protected health information. The exposure of admin tokens and potential remote code execution may result in non-compliance with these regulations.

Mitigation Strategies

Upgrade Yank Note to version 3.93.1 or apply the patch commit 59f85d48f17a70a402ad59dcecacdbec20f954df. Ensure the JWT secret is removed from API responses and restrict access to /api/settings endpoint.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-122154. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...