# gitoxide-core does not neutralize special characters for terminals

Advisory record · `GHSA-88g2-r9rw-g55h`

- **Identifiers:** `GHSA-88g2-r9rw-g55h` · `CVE-2024-43785` · `RUSTSEC-2024-0364`
- **State:** Confirmed
- **Severity:** CVSS 2.5 Low
- **Critical:** No
- **Weakness (CWE):** [CWE-150](https://cwe.mitre.org/data/definitions/150.html)
- **Tags:** [CWE-150](https://agentprime.io/advisories/tag/cwe-150.md)
- **Published:** 22 Aug 2024
- **Updated:** 12 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 22 Aug 2024, 12:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `gitoxide-core` (crates.io): affected `>=0.0.0-0`; no fixed version yet

## Machine-written summary

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

> GitoxideCore (crates.io package gitoxide-core, all versions) writes repository paths, author and committer names, commit messages and other metadata to terminals without neutralizing control characters, including ANSI escape sequences. An attacker who supplies a malicious repository that a user clones or operates in can make output misrepresent file names or alter and mimic error messages, with mostly limited effects. No fix is listed.

Written 3 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

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

- **CISA KEV:** Not listed.
- **EPSS:** 0.0020, the 9th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:24 UTC: First seen by agentprime
- 31 Oct 2026, 14:24 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/RUSTSEC-2024-0364)

## Sources

- [GitHub Advisory Database: GHSA-88g2-r9rw-g55h](https://github.com/advisories/GHSA-88g2-r9rw-g55h)
- [OSV: GHSA-88g2-r9rw-g55h](https://osv.dev/vulnerability/GHSA-88g2-r9rw-g55h)
- <https://crates.io/crates/gitoxide-core>
- <https://rustsec.org/advisories/RUSTSEC-2024-0364.html>
- <https://github.com/advisories/GHSA-88g2-r9rw-g55h>
- <https://nvd.nist.gov/vuln/detail/CVE-2024-43785>

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-88g2-r9rw-g55h>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-88g2-r9rw-g55h/>. Everything for agents: <https://agentprime.io/llms.txt>.