CVE-2026-86775

HIGHPre-NVD 8.68.6—
EchelonGraph scoreHIGH confidence

Score 8.6 from GitHub Security Advisory (severity: HIGH) published 2026-09-09. a secondary CVSS source baseline 8.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.6Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.6
EG Score
8.6(high)
EG Risk
54(Track)
EG Risk 54/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity86% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
53%
KEV
Not listed

Published

September 9, 2026

Last Modified

September 14, 2026

Advisory Details (2)

Auto-updated Sep 9, 2026
Patch available. Sources: github.
generic Patch Available

knowns before 0.30.0 Path Traversal via Document API | Advisories | VulnCheck

https://www.vulncheck.com/advisories/knowns-before-0.30.0-path-traversal-via-document-api
github Patch Available

Unrestricted Path Traversal in Document API allows Arbitrary .md File Read/Write/Delete + mkdir · Advisory · knowns-dev/knowns · GitHub

https://github.com/knowns-dev/knowns/security/advisories/GHSA-3h35-4jq7-hv45

Vendor Advisories for CVE-2026-86775(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 26× in last 7d / 68× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-25 05:25 UTCGHSA enrichment
  2. 2026-09-24 18:21 UTCEG score recompute
  3. 2026-09-24 18:21 UTCGHSA enrichment
  4. 2026-09-24 14:04 UTCEPSS rescore
  5. 2026-09-24 07:16 UTCGHSA enrichment
  6. 2026-09-23 20:12 UTCEG score recompute
  7. 2026-09-23 20:12 UTCGHSA enrichment
  8. 2026-09-23 17:54 UTCEPSS rescore
  9. 2026-09-23 09:08 UTCGHSA enrichment
  10. 2026-09-22 22:04 UTCEG score recompute
  11. 2026-09-22 22:04 UTCGHSA enrichment
  12. 2026-09-22 16:01 UTCEPSS rescore
  13. 2026-09-22 11:00 UTCGHSA enrichment
  14. 2026-09-21 23:56 UTCEG score recompute
  15. 2026-09-21 23:55 UTCGHSA enrichment
  16. 2026-09-21 21:09 UTCEPSS rescore
  17. 2026-09-21 12:51 UTCGHSA enrichment
  18. 2026-09-21 01:47 UTCGHSA enrichment
  19. 2026-09-20 14:42 UTCGHSA enrichment
  20. 2026-09-20 03:35 UTCGHSA enrichment
  21. 2026-09-19 16:31 UTCEG score recompute
  22. 2026-09-19 16:31 UTCGHSA enrichment
  23. 2026-09-19 05:26 UTCEG score recompute
  24. 2026-09-19 05:26 UTCGHSA enrichment
  25. 2026-09-18 19:28 UTCEPSS rescore
Show 43 more
  1. 2026-09-18 18:22 UTCGHSA enrichment
  2. 2026-09-18 07:18 UTCGHSA enrichment
  3. 2026-09-17 20:14 UTCEG score recompute
  4. 2026-09-17 20:14 UTCGHSA enrichment
  5. 2026-09-17 19:32 UTCEPSS rescore
  6. 2026-09-17 08:58 UTCGHSA enrichment
  7. 2026-09-16 21:54 UTCEG score recompute
  8. 2026-09-16 21:54 UTCGHSA enrichment
  9. 2026-09-16 14:09 UTCEPSS rescore
  10. 2026-09-16 10:49 UTCEG score recompute
  11. 2026-09-16 10:49 UTCGHSA enrichment
  12. 2026-09-16 05:15 UTCEPSS rescore
  13. 2026-09-15 23:45 UTCGHSA enrichment
  14. 2026-09-15 12:40 UTCEG score recompute
  15. 2026-09-15 12:40 UTCGHSA enrichment
  16. 2026-09-15 03:12 UTCEPSS rescore
  17. 2026-09-15 03:12 UTCEPSS rescore
  18. 2026-09-15 01:35 UTCGHSA enrichment
  19. 2026-09-14 14:31 UTCEG score recompute
  20. 2026-09-14 14:31 UTCGHSA enrichment
  21. 2026-09-14 13:40 UTCEG score recompute
  22. 2026-09-14 13:40 UTCGHSA enrichment
  23. 2026-09-14 05:43 UTCGHSA enrichment
  24. 2026-09-13 18:39 UTCEG score recompute
  25. 2026-09-13 18:39 UTCGHSA enrichment
  26. 2026-09-13 07:34 UTCGHSA enrichment
  27. 2026-09-12 20:31 UTCEG score recompute
  28. 2026-09-12 20:31 UTCGHSA enrichment
  29. 2026-09-12 09:27 UTCGHSA enrichment
  30. 2026-09-11 22:23 UTCEG score recompute
  31. 2026-09-11 22:23 UTCGHSA enrichment
  32. 2026-09-11 14:53 UTCEPSS rescore
  33. 2026-09-11 14:53 UTCEPSS rescore
  34. 2026-09-11 11:18 UTCEG score recompute
  35. 2026-09-11 11:17 UTCGHSA enrichment
  36. 2026-09-11 05:51 UTCGHSA enrichment
  37. 2026-09-10 18:47 UTCGHSA enrichment
  38. 2026-09-10 07:43 UTCGHSA enrichment
  39. 2026-09-09 20:39 UTCEG score recompute
  40. 2026-09-09 20:39 UTCGHSA enrichment
  41. 2026-09-09 14:26 UTCEG score recompute
  42. 2026-09-09 13:45 UTCEG score recompute
  43. 2026-09-09 13:44 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-86775?
CVE-2026-86775 is a high vulnerability published on September 9, 2026. 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 ../…
When was CVE-2026-86775 disclosed?
CVE-2026-86775 was first published in the National Vulnerability Database on September 9, 2026, with the most recent update on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-86775 actively exploited?
CVE-2026-86775 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 47.2% of all scored CVEs.
What is the CVSS score of CVE-2026-86775?
CVE-2026-86775 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2026-86775?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-86775, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-86775

Explore →

Is Your Infrastructure Affected by CVE-2026-86775?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.