Knowns-dev vulnerabilities
We track 12 vulnerabilities in Knowns-dev products. 12 are rated high or critical, and none are known to be exploited. The most recent was published on September 10, 2026.
Latest Knowns-dev vulnerabilities
- 8.3 High severity
knowns: Incorrect Authorization
knowns through 0.33.0 exempts the project.set action from permission guard checks unconditionally, allowing read-only agent sessions to bypass restrictions. Attackers can invoke project.set to repoint the server at another project directory and obtain write ac
- 8.8 High severity
knowns: Improper Limitation of a Pathname to a Restricted Directory
knowns through 0.33.0 fails to properly validate template destination paths in the code generation template engine, allowing attackers to read and write arbitrary files outside the project root. Attackers can supply malicious templates that traverse directorie
- 9.8 Critical severity
knowns: External Control of File Name or Path
knowns versions before 0.31.0 fail to properly validate the x-opencode-directory request header in the /api/opencode proxy endpoint. Remote attackers can supply arbitrary directory paths to execute file operations outside the project root on the host system.
- 8.6 High severity
knowns: Improper Limitation of a Pathname to a Restricted Directory
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
- 8.1 High severity
knowns: Incorrect Authorization
knowns versions before 0.30.0 contain an authorization bypass vulnerability where mutating code actions are incorrectly classified as read-only operations. Attackers with read-restricted sessions can exploit code.replace to modify permission configurations and
- 9.8 Critical severity
knowns: Missing Authentication for Critical Functionality
knowns versions before 0.30.0 serve the management API without authentication on all network interfaces by default, with no password required on fresh installations. Attackers can access the unauthenticated /api/tunnel/start endpoint to provision a public tunn
- 9.1 Critical severity
knowns: Improper Limitation of a Pathname to a Restricted Directory
knowns before 0.30.0 fails to validate import names in the import routes, allowing unauthenticated attackers to write files outside the imports directory. Attackers can supply traversal sequences in the name parameter to escape the imports directory and overwr
- 8.3 High severity
knowns: Improper Limitation of a Pathname to a Restricted Directory
knowns versions before 0.30.0 contain a path traversal vulnerability in the handleCodeReplace() function that allows attackers to overwrite arbitrary files outside the project root. Attackers can supply absolute paths or relative paths containing directory tra
- 7.8 High severity
knowns: Improper Neutralization of Special Elements used in an OS Command
knowns versions before 0.30.0 fail to validate the settings.lsp.languages binary field in project configuration files, allowing attackers to execute arbitrary binaries by crafting a malicious .knowns/config.json file. When a repository with a crafted configura
- 7.2 High severity
knowns: Server-Side Request Forgery
knowns through 0.33.0 contains a server-side request forgery vulnerability in the POST /api/embedding-models/test endpoint that issues outbound requests to caller-supplied destinations without validation. Attackers can enumerate internal hosts and cloud metada
- 7.5 High severity
knowns: Improper Limitation of a Pathname to a Restricted Directory
knowns versions before 0.30.0 contain a path traversal vulnerability in the POST /api/templates/preview endpoint that allows unauthenticated attackers to read arbitrary files. Attackers can supply directory traversal sequences in the templateFile parameter to
- 8.8 High severity
knowns: Improper Limitation of a Pathname to a Restricted Directory
knowns versions before 0.30.0 fail to validate filesystem paths in MCP tool arguments, allowing attackers to read, create, overwrite and delete files outside the project directory. Attackers can supply path arguments containing directory traversal sequences to