---
id: "CVE-2026-129157"
page: "https://infrastack.ai/live/CVE-2026-129157"
kind: "vulnerability"
aliases: ["CVE-2026-129157"]
title: "ragent: any logged-in user can read other users' RAG traces"
severity: "medium"
cvss: 5.3
epss: null
exploited: false
status: "open"
category: "ai-tooling"
products: [{"name": "ragent", "fixed": [], "affected": ">= 1.0.0, <= 1.1.0", "ecosystem": "github"}]
ecosystems: []
tags: ["ai-tooling", "multi-user", "rag", "ragent", "self-hosted"]
not_affected_if: ["auth-required", "single-user", "trace-endpoints-blocked"]
published_at: "2026-11-13T18:17:40+00:00"
first_seen_at: "2026-11-13T18:49:30+00:00"
updated_at: "2026-11-13T18:52:39+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-129157", "first_seen_at": "2026-11-13T18:49:30+00:00"}, {"source": "analyst", "url": "https://github.com/nageoffer/ragent/issues/186", "first_seen_at": "2026-11-13T18:52:39+00:00", "cites": ["https://github.com/nageoffer/ragent/issues/186", "https://vul.yulun.ac.cn/20261104/ragent/"]}]
exploit_sources: [{"type": "poc", "url": "https://vul.yulun.ac.cn/20261104/ragent/"}]
---

# ragent: any logged-in user can read other users' RAG traces

Link for people: https://infrastack.ai/live/CVE-2026-129157 (this .md is for agents)

ragent 1.0.0 through 1.1.0 has a missing authorization check in its RagTraceController, so any signed-in user can list all users' RAG traces. An attacker can read other users' usernames, user ids, conversation ids, questions and per-node execution details through the /rag/traces endpoints.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- github:ragent affected >= 1.0.0, <= 1.1.0 fixed no fixed version listed

## How to check

- Check your ragent version: 1.0.0 through 1.1.0 are affected (the report reproduced it on commit c3b6157).
- Log in as a non-admin user and request GET /api/ragent/rag/traces/runs?pageNo=1&pageSize=5. If it returns 200 with other users' questions and usernames, you are exposed. /users returning a permission error for the same user does not mean the trace endpoint is protected.

## Fix

No fixed version published as of 2026-11-13; issue #186 is still open. Until a patch ships, block /rag/traces/* at the reverse proxy or restrict it to admins, and limit accounts to trusted users.

## Timeline

- 2026-11-13T18:49:30+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-129157
- 2026-11-13T18:52:39+00:00 analyst https://github.com/nageoffer/ragent/issues/186 — Read VulnCheck advisory, researcher report (vul.yulun.ac.cn) and maintainer GitHub issue #186 (open since 2026-11-04, no maintainer reply or fixed release seen). Public PoC in the report; no exploitation reported.

## Documents

- [advisory] Third-party advisory: www.vulncheck.com https://www.vulncheck.com/advisories/ragent-1.0.0-through-1.1.0-missing-authorization-via-rag-traces-runs
- [advisory] ragent #186: regular user can read /rag/traces/runs https://github.com/nageoffer/ragent/issues/186
- [poc] Ragent Vulnerability Report (Wu Yulun) https://vul.yulun.ac.cn/20261104/ragent/

## From the sources

ragent 1.0.0 through 1.1.0 contains a missing authorization vulnerability in RagTraceController that allows any logged-in user to view all users' RAG traces. Attackers can page through /rag/traces/runs and related node endpoints to read other users' usernames, user ids, conversation ids, questions, and per-node execution details.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_