CVE-2026-115509 Jitsu Console before 2.14.0-beta.41 Cross-Workspace Authorization Bypass via sources/state API
Low 2.3
Published
Updated
Check this codebase for CVE-2026-115509 and fix it if it is affected.
What it is: CVE-2026-115509 is a low-severity vulnerability in jitsucom jitsu, published on 22 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-115509 in the wild and no public exploit code.
Affected product: jitsucom jitsu. 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-115509/ (Markdown: https://insights.sbomify.com/CVE-2026-115509/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-115509?
CVE-2026-115509 is a low-severity vulnerability in jitsucom jitsu, published on 22 Oct 2026.
Official description
Jitsu console before 2.14.0-beta.41 contains an incorrect authorization vulnerability in sources/state.ts handlers that call findFirst without await, so the syncId ownership check never fails. Authenticated users knowing another workspace's sync ID can read, overwrite or delete its stream cursors, causing data re-ingestion or skipped data.
Weakness: CWE-863
Which versions are affected by CVE-2026-115509?
How do I fix CVE-2026-115509?
No fix has been published for CVE-2026-115509 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-115509 being exploited?
There is no known exploitation of CVE-2026-115509 in the wild and no public exploit code.
Sources
Also known as GHSA-vfq9-5jrr-qr65.