# NoneBot Potential Information Leak in User-Constructed Message Templates

Advisory record · `GHSA-59j8-776v-xxxg`

- **Identifiers:** `GHSA-59j8-776v-xxxg` · `CVE-2024-21624` · `PYSEC-2024-37`
- **State:** Confirmed
- **Severity:** CVSS 5.7 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-1336](https://cwe.mitre.org/data/definitions/1336.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [Code injection](https://agentprime.io/advisories/tag/code-injection.md)
- **Published:** 9 Feb 2024
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 9 Feb 2024, 15:04 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `nonebot2` (PyPI): affected `>=2.0.0a16, <2.2.0`; fixed in `2.2.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> NoneBot (nonebot2) versions 2.0.0a16 up to 2.2.0 are affected. When developers put user-provided data into a MessageTemplate, an attacker can cause an information leak, such as environment variables. Upgrade nonebot2 to 2.2.0 or later. As a temporary workaround, filter underscores from user input before adding it to the message template.

Written 5 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.7 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0049, the 42nd percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:36 UTC: First seen by agentprime
- 31 Oct 2026, 14:36 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-59j8-776v-xxxg)

## Sources

- [GitHub Advisory Database: GHSA-59j8-776v-xxxg](https://github.com/advisories/GHSA-59j8-776v-xxxg)
- [OSV: GHSA-59j8-776v-xxxg](https://osv.dev/vulnerability/GHSA-59j8-776v-xxxg)
- <https://github.com/nonebot/nonebot2/security/advisories/GHSA-59j8-776v-xxxg>
- <https://nvd.nist.gov/vuln/detail/CVE-2024-21624>
- <https://github.com/nonebot/nonebot2/pull/2509>
- <https://github.com/nonebot/nonebot2/commit/b65b3b438c95894654fd9081139989c757bdc6c1>
- <https://github.com/nonebot/nonebot2>
- <https://github.com/pypa/advisory-database/tree/main/vulns/nonebot2/PYSEC-2024-37.yaml>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-59j8-776v-xxxg>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-59j8-776v-xxxg/>. Everything for agents: <https://agentprime.io/llms.txt>.
