# CVE-2026-29872: Information disclosure in n/a

> Attackers can retrieve other users' API tokens due to lack of session isolation in a Streamlit-based GitHub MCP Agent, leading to unauthorized access.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Mar 2026
- **Updated:** 30 Mar 2026
- **Also known as:** GHSA-qx64-h3hh-3vhj

## What is CVE-2026-29872?

CVE-2026-29872 is a high-severity vulnerability in n/a, published on 30 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A cross-session information disclosure vulnerability exists in the awesome-llm-apps project in commit e46690f99c3f08be80a9877fab52acacf7ab8251 (2026-01-19). The affected Streamlit-based GitHub MCP Agent stores user-supplied API tokens in process-wide environment variables using os.environ without proper session isolation. Because Streamlit serves multiple concurrent users from a single Python process, credentials provided by one user remain accessible to subsequent unauthenticated users. An attacker can exploit this issue to retrieve sensitive information such as GitHub Personal Access Tokens or LLM API keys, potentially leading to unauthorized access to private resources and financial abuse.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Theunwindai Awesome Llm Apps.

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

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

## Is CVE-2026-29872 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-29871](https://insights.sbomify.com/CVE-2026-29871/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-29872 is a high-severity vulnerability in n/a, published on 30 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-29872 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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