CVE-2026-86775
Last modified
CVE-2026-86775 is a high-severity vulnerability rated 8.6/10 on the CVSS scale. knowns (npm package) versions <= 0.29.1 contain a path traversal vulnerability in the Document API. The HTTP handler in internal/server/routes/docs.go normalizes the user-supplied document path with cleanDocPath(), which strips leading/trailing slashes and the .md suffix but does not neutralize ../ traversal sequences, and internal/storage/doc_store.go then builds the target path with filepath.Join(ds.docsDir(), filepath.FromSlash(doc.Path)+".md") without verifying that the resolved path remains inside the documents directory.
Description
knowns (npm package) versions <= 0.29.1 contain a path traversal vulnerability in the Document API. The HTTP handler in internal/server/routes/docs.go normalizes the user-supplied document path with cleanDocPath(), which strips leading/trailing slashes and the .md suffix but does not neutralize ../ traversal sequences, and internal/storage/doc_store.go then builds the target path with filepath.Join(ds.docsDir(), filepath.FromSlash(doc.Path)+".md") without verifying that the resolved path remains inside the documents directory. In the default deployment, where the Management API is unauthenticated and bound to all interfaces, a remote unauthenticated attacker can supply a traversal payload (for example {"path": "../../../../tmp/knowns_pwn_marker"} to POST /api/docs, or an encoded path to GET /api/docs/...) to read, create, overwrite, or delete arbitrary files with a .md extension anywhere on the host filesystem and to create arbitrary directories via os.MkdirAll. This can expose sensitive data stored in other projects' documentation, corrupt or destroy files, and provide an arbitrary-write primitive that may be chained toward code execution. The issue is fixed in version 0.30.0.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| knowns-dev | knowns | < 0.30.0 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-86775?
How severe is CVE-2026-86775?
How do I fix CVE-2026-86775?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-8677The Prime Elementor Addons – Lightweight Elementor Widgets f…6.4
- CVE-2026-86770Snipe-IT before 8.7.0 fails to validate username case sensit…8.1
- CVE-2026-86771Snipe-IT versions before 8.7.0 fail to HTML-escape the emplo…7.6
- CVE-2026-86772Snipe-IT versions before 8.7.0 contain a stored cross-site s…5.4
- CVE-2026-86773Snipe-IT through version 8.6.3 fails to perform object-level…5.4
- CVE-2026-86774Snipe-IT versions before 8.7.0 contain a broken access contr…6.3
- CVE-2026-86776KeePass versions 2.35 through 2.61.1 fail to validate KDBX h…3.3
- CVE-2026-86777AlchemyCMS versions before 7.4.16 and 8.x before 8.3.6 fail …5.3
- CVE-2026-8678The MyParcel plugin for WordPress is vulnerable to authoriza…4.3
- CVE-2026-8679The AudioIgniter plugin for WordPress is vulnerable to Insec…7.5
- CVE-2026-8680Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2026-86804A vulnerability was identified in seakee CPA-Manager-Plus up…5.3
Are you affected by CVE-2026-86775?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
