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


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-gwx5-24gg-jphv

## What is CVE-2026-129157?

CVE-2026-129157 is a medium-severity vulnerability in nageoffer ragent, published on 13 Nov 2026. 

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-129157?

1 open source package ship an affected version, including nageoffer/ragent.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `nageoffer/ragent` | GitHub | `pkg:github/nageoffer/ragent` | From 1.0.0 to 1.1.0 | None |

## How do I fix CVE-2026-129157?

No fix has been published for CVE-2026-129157 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-129157 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-129157 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-129157 and fix it if it is affected.

What it is: CVE-2026-129157 is a medium-severity vulnerability in nageoffer ragent, published on 13 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-129157 exists.

Affected packages and fixed versions:
- nageoffer/ragent (GitHub): affected from 1.0.0 up to 1.1.0; no fix listed

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-129157/ (Markdown: https://insights.sbomify.com/CVE-2026-129157/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-129157
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-129157
- OSV: https://osv.dev/vulnerability/CVE-2026-129157

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-129157/
Summaries are generated and may contain mistakes; the official description above is the record.
