@AUTH0/AI · CVE-2026-107372 · AI agents & MCP
FIX → 6.0.3 ✓ verified
The auth0-ai-js FGA retriever fails to tell apart authorization checks run under different conditions when filtering documents for retrieval-augmented generation. Documents that Auth0 FGA denies can therefore end up in the model context and in the generated response.
first public Nov 10, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Apps using the auth0-ai-js (@auth0/ai) FGA retriever for RAG with Auth0 FGA conditional checks, where one retrieval returns several documents that share the same object, user and relation but differ by authorization context. Then documents FGA denied can reach the model context and the response. Teams not using the FGA retriever, or using only unconditional FGA checks, can skip it.
Not affected if no-conditional-checks, no-fga-retriever, no-rag
Who cares auth0, fga, javascript, llm, npm, rag
npm ls @auth0/ai (or check package-lock.json / pnpm-lock.yaml / yarn.lock): versions <= 6.0.2 are affectedThe auth0-ai-js FGA retriever does not distinguish between authorization checks under different conditions when filtering documents during retrieval-augmented generation, resulting in documents denied by Auth0 FGA being included in the model context and used in the generated response.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
Upgrade to 6.0.3
Upgrade @auth0/ai to 6.0.3 or later.