Skip to main content
VulnerabilityPublished

CVE-2026-122157: Purocean Yank Note · Command Injection

Affects ynSource GCVE Database

0
Compare
Authoritative record:CVE-2026-122157· Medium 5.3

Public exploit available · CVSS 5.3 Medium · fixed in 3.93.1 : patch yn as a priority.

Data as of 5 Nov 2026, 04:29 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulDB)CVSS 4.05.3
CNA (VulDB)CVSS 3.16.3
CNA (VulDB)CVSS 3.06.3
CNA (VulDB)CVSS 2.07.5
Patch
Available – fixed in 3.93.1
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubpurocean/ynpkg:github/purocean/ynOther threatsAffected
  • =3.93.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Purocean Yank Note to version 3.93.1, which contains the official fix for this vulnerability. Applying this update remediates the OS command injection issue in the Terminal Handler component. No additional mitigations are specified.

Description

A remote OS command injection vulnerability exists in Purocean Yank Note version 3.93.0 within the checkPermission function of the Terminal Handler component. This flaw allows an attacker to execute arbitrary operating system commands remotely. The vulnerability is addressed by upgrading to version 3.93.1.

References

Community reviews

Loading reviews…