# CVE-2026-122154: purocean Yank Note Settings Endpoint index.ts config.getAll information disclosure


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 5 Nov 2026
- **Updated:** 5 Nov 2026
- **Also known as:** GHSA-gc7g-q4vc-cx9r

## What is CVE-2026-122154?

CVE-2026-122154 is a medium-severity vulnerability in purocean Yank Note, published on 5 Nov 2026. 

### Official 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.

Weakness: CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-122154?


## How do I fix CVE-2026-122154?

No fix has been published for CVE-2026-122154 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-122154 being exploited?

There is no known exploitation of CVE-2026-122154 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-122154 and fix it if it is affected.

What it is: CVE-2026-122154 is a medium-severity vulnerability in purocean Yank Note, published on 5 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-122154 in the wild and no public exploit code.

Affected product: purocean Yank Note. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-122154/ (Markdown: https://insights.sbomify.com/CVE-2026-122154/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-122154
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-122154
- OSV: https://osv.dev/vulnerability/CVE-2026-122154

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-122154/
Summaries are generated and may contain mistakes; the official description above is the record.