CVE-2026-29872: Improper Access Control
Source CVE Database V5
Not known to be exploited · CVSS 8.2 High.
Data as of 26 Oct 2026, 12:55 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
To mitigate CVE-2026-29872, developers should avoid storing user-supplied API tokens in process-wide environment variables. Instead, implement per-session or per-user secure storage mechanisms that isolate credentials, such as in-memory session stores or encrypted databases scoped to individual users. Refactor the application to run each user session in isolated processes or containers where environment variables are not shared. Use Streamlit's session state features or external secure vaults to manage sensitive tokens safely. Additionally, enforce strict access controls and audit logging to detect unauthorized access attempts. Regularly rotate API tokens and implement least privilege principles for token scopes. For existing deployments, immediately review and revoke any potentially exposed tokens and update the application to a patched version once available. Conduct thorough security testing focusing on multi-user session isolation in Streamlit apps. Educate developers on secure credential handling best practices to prevent similar issues.
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.