CVE-2026-115333 Lotus through 0.10.2 Improper Authentication via Event Ingestion API Key Prefix
High 8.2
Published
Updated
Check this codebase for CVE-2026-115333 and fix it if it is affected.
What it is: CVE-2026-115333 is a high-severity vulnerability in uselotus lotus, published on 22 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-115333 in the wild and no public exploit code.
Affected product: uselotus lotus. 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-115333/ (Markdown: https://insights.sbomify.com/CVE-2026-115333/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-115333?
CVE-2026-115333 is a high-severity vulnerability in uselotus lotus, published on 22 Oct 2026.
Official description
Lotus through 0.10.2 contains an improper authentication vulnerability in the Go event ingestion middleware that validates API keys by prefix only, without checking the secret against the stored hashed_key. Attackers who know or obtain an API key prefix can submit usage events to POST /api/track/ as that organization, altering its metered usage and billing.
Weakness: CWE-287
Which versions are affected by CVE-2026-115333?
How do I fix CVE-2026-115333?
No fix has been published for CVE-2026-115333 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-115333 being exploited?
There is no known exploitation of CVE-2026-115333 in the wild and no public exploit code.
Sources
Also known as GHSA-pcv2-4g25-r7qr.