Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-86775 – Unauthenticated Path Traversal (Arbitrary File Read/Write/Delete) – knowns npm pack

Be the first to know when new zero-days emerge:

Summary

CVE-2026-86775 is a path traversal vulnerability (CWE-22) in the Document API of the knowns npm package, an open-source "memory layer" service that gives AI coding agents persistent access to project documentation and context. Versions up to and including 0.29.1 fail to neutralize ../ sequences in user-supplied document paths, allowing a remote, unauthenticated attacker to read, create, overwrite, or delete arbitrary files on the host filesystem. The flaw is rated High severity (CVSS 8.8) and is fixed in version 0.30.0.

Technical details

  • Root cause: The HTTP handler in internal/server/routes/docs.go normalizes the incoming document path via a cleanDocPath() function that strips leading/trailing slashes and the .md suffix, but does not strip or reject ../ traversal sequences.
  • Trigger conditions: internal/storage/doc_store.go then constructs the on-disk file path using filepath.Join(ds.docsDir(), filepath.FromSlash(doc.Path)+".md") without verifying that the resulting resolved path stays inside the intended documents directory.
  • Attack vector: In knowns’ default deployment, the Management API is unauthenticated and bound to all network interfaces. A remote attacker can send a crafted request such as {"path": "../../../../tmp/knowns_pwn_marker"} to POST /api/docs, or an encoded traversal path to GET /api/docs/..., with no authentication or user interaction required.
  • Impact: Successful exploitation lets an attacker read sensitive files stored outside the intended documents directory (e.g., other projects’ documentation or secrets), overwrite or delete arbitrary .md files anywhere on the host, and create arbitrary directories via os.MkdirAll. Because writes are not restricted to the project sandbox, this arbitrary-write primitive could potentially be chained toward further compromise, including code execution, depending on the deployment.

Affected software

  • Vendor/Project: knowns-dev
  • Package: knowns (npm, pkg:npm/knowns)
  • Affected versions: All versions ≤ 0.29.1
  • Fixed version: 0.30.0 (and later)

Severity

  • CVSS v3.1 Base Score: 8.6 (High) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L
  • CVSS v4.0 Base Score: 8.8 (High) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N
  • Attack vector: Network, no privileges or user interaction required.

Mitigation and recommended actions

  • Immediate: Upgrade the knowns npm package to version 0.30.0 or later, which fixes the path validation logic to properly contain document paths within the documents directory.
  • If immediate patching is not possible:
    • Do not expose the knowns Management/Document API on untrusted networks or bind it to all interfaces; restrict it to localhost or place it behind authentication and a firewall/VPN.
    • Monitor and restrict outbound file operations from the service account running knowns to the minimum required directories.
    • Audit logs for requests to /api/docs containing ../ or encoded traversal sequences, and for unexpected .md files created/modified/deleted outside the expected documents directory.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge