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?
- Critical severity, with a CVSS score of 9.8, published 10 September 2026.
- Which products and versions are affected?
- Knowns Knowns < 0.31.0.
- Is there a fix for This vulnerability?
- A patch was published on 2026-09-10: Fix released in v0.31.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 over the network.
- Am I affected?
- Check whether anything you run is named in the advisory. 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.
Technical details
The vulnerability is an external control of file name or path (CWE-73) flaw in the /api/opencode proxy endpoint. The server fails to properly validate the x-opencode-directory request header, allowing attackers to inject arbitrary directory paths. An unauthenticated remote attacker can exploit this over the network with low complexity to execute file operations outside the project root directory, achieving full confidentiality, integrity, and availability compromise of the host filesystem. Versions before 0.31.0 are affected; a patch is available in version 0.31.0 or later.
Affected products
- Knowns Knowns < 0.31.0
Timeline
- 2026-09-10: disclosed
- 2026-09-10: advisory: GHSA-w47m-jpv2-qfw5 published; marked as duplicate of GHSA-9h2q-r9fh-f98w
- 2026-09-10: patched: Fix released in v0.31.0