CVE-2026-111915: Yank Note before 3.93.1 Path Traversal via /api/help Endpoint
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
Yank Note before 3.93.1 contains a path traversal vulnerability that allows unauthenticated remote attackers to read arbitrary files via the path or doc parameter of /api/help. Attackers can supply repeated ‘../‘ segments, which bypass the single-replacement sanitization in the publicly allowlisted endpoint, to read SSH keys, configuration, or notes.
Description quoted from the CVE record (assigned by VulnCheck, published 2026-10-19).
Weakness: Improper Limitation of a Pathname to a Restricted Directory (‘Path Traversal’)
How it can be exploited
Exploitable over the network with high attack complexity only when specific conditions are present needing no privileges and no user interaction. Impact: confidentiality high, integrity none, availability none. CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: partial.
Public exploit evidence (Exploit Observer)
Also known as: EUVD-2026-104318, GHSA-46p6-h3r3-3fvj
VEDAS cluster: VEDAS:DOGWOODDUGONG
Exploit Observer links 5 pieces of public exploit code or detection modules that name this CVE or one of its aliases.
Exploit code and modules (5)
Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/nuclei/2026/CVE-2026-111915.yaml
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/nuclei/2026/CVE-2026-111915.yaml
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-111915.rules
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-111915.rules
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-111915.rules
Vulnerability databases and vendor advisories (3)
Catalogue entries, not exploit evidence.
- Vulnerability database or vendor advisory: https://euvd.enisa.europa.eu/enisa/EUVD-2026-104318
- Vulnerability database or vendor advisory: https://github.com/advisories/GHSA-46p6-h3r3-3fvj
- Vulnerability database or vendor advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-111915
2 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.
VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.
Live scores
- EPSS
- 0.005
low predicted chance of attack - VEDAS
- 0.986
strong exploit evidence - On CISA KEV
- Not listed
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| purocean Yank Note | before 3.93.1 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
Fixed versions stated in the CVE record: 3.93.1.
Vendor guidance:
- https://github.com/purocean/yn/commit/d3b0ad27f7f6388b878eefd828557ae2d2a8789b (patch)
- Yank Note v3.93.1 Release Notes (release-notes)
How to detect it
Nuclei template (active check)
Yank Note - Path Traversal
Yank Note before 3.93.1 exposes an unauthenticated arbitrary file read on the publicly allowlisted GET /api/help endpoint. The handler sanitises the path (and doc) query parameter with a single JavaScript String.replace(‘../‘,’’) call, which removes only the first traversal segment, so repeated ../ sequences still escape the help directory. This template requests /api/help with a traversal payload in the path parameter and confirms the contents of /etc/passwd are returned to an unauthenticated caller.
Name and description quoted from the template, written by VEDAS.
The template sends 1 request (GET /api/help?path=../../../../../../../../../../etc/passwd); it decides using regex, status matchers. Severity in the template: high. Marked as not yet verified against a live vulnerable target.
Run it against a host you own or are authorised to test:
nuclei -u https://your-host -t CVE-2026-111915.yamlShow the template (41 lines)
id: CVE-2026-111915
info:
name: "Yank Note - Path Traversal"
author: vedas-arpsyndicate
severity: high
description: |
Yank Note before 3.93.1 exposes an unauthenticated arbitrary file read on the publicly
allowlisted GET /api/help endpoint. The handler sanitises the path (and doc) query
parameter with a single JavaScript String.replace('../','') call, which removes only the
first traversal segment, so repeated ../ sequences still escape the help directory. This
template requests /api/help with a traversal payload in the path parameter and confirms
the contents of /etc/passwd are returned to an unauthenticated caller.
reference:
- https://www.exploit.observer/?keyword=CVE-2026-111915&match=exact
- https://subdomain.center/?engine=ammonites&keyword=yank-note&match=exact
classification:
cvss-metrics: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
cvss-score: 7.5
cve-id: CVE-2026-111915
cwe-id: CWE-22
metadata:
verified: false
tags: cve,cve2026,yank-note,lfi,traversal,unauth
http:
- raw:
- |
GET /api/help?path=../../../../../../../../../../etc/passwd HTTP/1.1
Host: {{Hostname}}
Accept: application/octet-stream
matchers-condition: and
matchers:
- type: regex
part: body
regex:
- "root:.*:0:0:"
- type: status
status:
- 200
CVE-2026-111915.yaml on GitHub
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-111915 Yank Note - Path Traversal. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-111915 Yank Note - Path Traversal"; flow:established,to_server; http.method; content:"GET"; http.uri.raw; content:"/api/help"; nocase; fast_pattern; pcre:"/[?&](?:path|doc)=[^&]*(?:\.\.(?:\x2f|%2f)|%2e%2e)/i"; classtype:web-application-attack; reference:cve,CVE-2026-111915; reference:url,https://www.exploit.observer/?keyword=CVE-2026-111915&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=yank-note&match=exact; sid:1084200; rev:1;)
CVE-2026-111915.rules on GitHub
References
Vendor advisories and patches
- https://github.com/purocean/yn/commit/d3b0ad27f7f6388b878eefd828557ae2d2a8789b (patch)
- Yank Note v3.93.1 Release Notes (release-notes)
Exploits and technical analysis
- https://github.com/purocean/yn/issues/543 (issue-tracking)
- https://github.com/purocean/yn/blob/v3.93.0/src/main/server/index.ts (technical-description)
- VulnCheck Advisory: Yank Note before 3.93.1 Path Traversal via /api/help Endpoint (third-party-advisory)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.