CVE-2026-129157: ragent 1.0.0 through 1.1.0 Missing Authorization via /rag/traces/runs

Q: Who can exploit this issue?

Any authenticated ragent user can exploit it. The attacker does not need elevated privileges or user interaction.

Q: What information can an attacker access?

An attacker can enumerate RAG trace runs and related node data belonging to other users. Exposed information includes usernames, user IDs, conversation IDs, questions, and per-node execution details.

Q: Are deployments affected by default?

The issue affects ragent versions 1.0.0 through 1.1.0 and is reachable through the /rag/traces/runs endpoint and related node endpoints for logged-in users.

Q: What can be done if patching is not immediately possible?

The provided information does not identify a workaround. Restricting access to affected trace endpoints to only trusted users may reduce exposure until an authorization fix is available.

Published Nov 13, 2026

Updated

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.

Affected Software

1 affected component

ragent>=1.0.0<=1.1.0

Event History

Nov 13, 2026

CVE Published

via MITRE·05:21 PM

Data Sourced

via MITRE·05:21 PM

DescriptionSeverityWeakness

Data Sourced

via NVD·06:17 PM

DescriptionSeverityWeakness

Frequently Asked Questions

Who can exploit this issue?

Any authenticated ragent user can exploit it. The attacker does not need elevated privileges or user interaction.

What information can an attacker access?

An attacker can enumerate RAG trace runs and related node data belonging to other users. Exposed information includes usernames, user IDs, conversation IDs, questions, and per-node execution details.

Are deployments affected by default?

The issue affects ragent versions 1.0.0 through 1.1.0 and is reachable through the /rag/traces/runs endpoint and related node endpoints for logged-in users.

What can be done if patching is not immediately possible?

The provided information does not identify a workaround. Restricting access to affected trace endpoints to only trusted users may reduce exposure until an authorization fix is available.

CVE-2026-129157: ragent 1.0.0 through 1.1.0 Missing Authorization via /rag/traces/runs

Affected Software

Event History

Frequently Asked Questions

Who can exploit this issue?

What information can an attacker access?

Are deployments affected by default?

What can be done if patching is not immediately possible?

Company

Resources

Contact

Frequently Asked Questions

Who can exploit this issue?

What information can an attacker access?

Are deployments affected by default?

What can be done if patching is not immediately possible?