CVE-2026-86542

9.1

knowns-dev · knowns

Knowns before 0.30.0 contains a path traversal vulnerability in import routes, allowing unauthenticated attackers to overwrite arbitrary files on the server.

Executive summary

A critical path traversal vulnerability in knowns-dev knowns allows unauthenticated attackers to overwrite files on the host system, posing a severe risk of system compromise.

Vulnerability

The application fails to validate the name parameter within import routes. This allows an unauthenticated attacker to use directory traversal sequences to escape the intended directory and overwrite any file accessible to the server process.

Business impact

The ability to overwrite arbitrary files on the server is a critical security failure, as it can lead to remote code execution or complete system takeover. Given the CVSS score of 9.1, this vulnerability is classified as critical, as it allows an unauthenticated actor to bypass all security controls and manipulate sensitive system files. Successful exploitation could result in total loss of confidentiality, integrity, and availability for the affected host.

Remediation

Immediate Action: Upgrade knowns-dev knowns to version 0.30.0 or later immediately to incorporate the necessary input validation fixes.

Proactive Monitoring: Review web server access logs for requests containing suspicious directory traversal patterns, such as sequences involving double dots and slashes, directed at the import endpoints.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to block requests containing path traversal payloads, particularly those targeting the /api/imports endpoint.

Exploitation status

Public Exploit Available: No

Analyst recommendation

This vulnerability represents a critical risk to the integrity of the hosting environment. Organizations must prioritize the update to version 0.30.0, as the lack of authentication requirements makes this flaw highly accessible to external threats. If patching is not immediately feasible, restrict access to the application endpoints until the update can be applied.

More knowns-dev CVEs

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief critical section

Sources

Originally found and disclosed by Tong Hoang Gia, Nguyen Huy Hoang, per the CVE Program record.