# CVE-2026-88939: knowns through 0.33.0 Authorization Bypass via project.set Bootstrap Exemption

> Attackers can bypass permission checks to gain write access by repointing the server to another project directory.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-qwj4-f78f-jj3j

## What is CVE-2026-88939?

CVE-2026-88939 is a high-severity authentication bypass vulnerability in knowns-dev knowns, published on 10 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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 access capabilities.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-88939?


## How do I fix CVE-2026-88939?

No fix has been published for CVE-2026-88939 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-88939 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-88939 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-88939 and fix it if it is affected.

What it is: CVE-2026-88939 is a high-severity authentication bypass vulnerability in knowns-dev knowns, published on 10 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-88939 exists.

Affected product: knowns-dev knowns. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-88939/ (Markdown: https://insights.sbomify.com/CVE-2026-88939/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-88939
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-88939
- OSV: https://osv.dev/vulnerability/CVE-2026-88939

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-88939/
Summaries are generated and may contain mistakes; the official description above is the record.