CVE-2026-33265 affects LibreChat 0.8.1-rc2, where a logged-in user obtains a JWT that is valid for both the LibreChat API and the RAG API. NVD scores it 6.3, medium. The record names no fixed version, so check the project and the SBA Research advisory before upgrading.
What's affected
LibreChat 0.8.1-rc2. The record lists no other versions and no fixed release. I could not confirm a patched version from the pages I read, so check the LibreChat releases and the advisory below before you decide which build to run.
The SBA Research notice says the release uses the same JWT secret for the user session mechanism and for the RAG API, which undermines the service level authentication of the RAG API.
How to check if you're exposed
Check which LibreChat version you deploy. For a container install, read the image tag in your compose file. For a source install, read the version in package.json.
Then check how your RAG API is reached. If it is only reachable from the LibreChat host and the JWT secret is shared, a user token may be accepted by it. Read the SBA Research advisory for the exact behavior they describe.
Paste your lockfile into the free in-browser dependency scan to see which versions you resolve, including transitive ones. Gold also lists this CVE on its directory page.
What to do now
- Identify whether you run 0.8.1-rc2, and move to a newer release that the project says addresses this.
- Do not expose the RAG API directly to users or the internet.
- If the shared secret has been used by untrusted users, rotate it after upgrading.
- Use separate secrets for user sessions and service to service calls where your configuration allows it.
Why it matters
The weakness class is CWE-669, incorrect resource transfer between spheres. A token meant to prove who a user is also works as a credential for an internal service. When one secret signs both, the boundary between user identity and service identity disappears.
The score is moderate because the vector needs a local, logged in user. Even so, a RAG service often sits next to private documents, so the practical impact depends on what yours indexes. The record does not flag this CVE as known exploited.
Quick check
Is there a confirmed fixed version?
Not in the record or the pages I read. Check the LibreChat releases and the SBA Research advisory for the current guidance.
Sources
Last reviewed: 19 October 2026.
