# CVE-2026-122157: Purocean Yank Note Terminal index.ts checkPermission os command injection


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/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-5qjp-6ppp-5274

## What is CVE-2026-122157?

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

### Official description

A vulnerability was identified in Purocean Yank Note 3.93.0. Affected by this vulnerability is the function checkPermission of the file src/main/server/index.ts of the component Terminal Handler. Such manipulation leads to os command injection. The attack can be executed remotely. The exploit is publicly available and might be used. Upgrading to version 3.93.1 addresses this issue. The name of the patch is 59f85d48f17a70a402ad59dcecacdbec20f954df. Upgrading the affected component is recommended.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-77 (Improper Neutralization of Special Elements used in a Command)

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


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

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

## Is CVE-2026-122157 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-122157 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-122157 is a medium-severity vulnerability in Purocean Yank Note, published on 5 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-122157 exists.

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-122157/ (Markdown: https://insights.sbomify.com/CVE-2026-122157/index.md)
```

## Sources

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

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