Is This vulnerability exploited in the wild?

No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

How severe is This vulnerability?

High severity, with a CVSS score of 7.8, published 8 September 2026.

Which products and versions are affected?

Knowns-Dev Knowns before 0.30.0; knowns (npm) < 0.30.0.

Is there a fix for This vulnerability?

Yes: fixed in 0.30.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is This vulnerability attacked?

It is attacked with local access, in a software library.

Check whether you run Knowns-Dev Knowns or knowns (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

knowns command injection in LSP binary configuration

Q: Is there a fix for This vulnerability?

Yes: fixed in 0.30.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is This vulnerability attacked?

It is attacked with local access, in a software library.

Q: Am I affected?

Check whether you run Knowns-Dev Knowns or knowns (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Severity: high · CVSS 7.8 · Published 2026-09-08

knowns is a development tool that manages project configurations. Versions before 0.30.0 fail to validate binary paths specified in project settings, allowing an attacker to execute arbitrary code by placing a malicious configuration file in a repository. When a developer opens the compromised repository, the attacker's code runs automatically under the developer's account.

Technologies: Knowns-Dev Knowns, knowns (npm). Vendors: Knowns-Dev, npm.

Quick answers

Is This vulnerability exploited in the wild?: No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?: High severity, with a CVSS score of 7.8, published 8 September 2026.
Which products and versions are affected?: Knowns-Dev Knowns before 0.30.0; knowns (npm) < 0.30.0.
Is there a fix for This vulnerability?: Yes: fixed in 0.30.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is This vulnerability attacked?: It is attacked with local access, in a software library.
Am I affected?: Check whether you run Knowns-Dev Knowns or knowns (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 0.30.0

Technical details

The vulnerability exists in the settings.lsp.languages binary field parsing within .knowns/config.json project configuration files. The application fails to validate or sanitize the binary path before execution, and executes the unvalidated path twice without verification. Attack requires local access to craft the malicious config file and user interaction to open the repository, but requires no elevated privileges.

Affected products

knowns-dev knowns before 0.30.0

Timeline

2026-09-08: disclosed

References

https://api.github.com/users/satyam-umrao

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.