# Denial of service when processing Git credentials in github.com/rancher/wrangler

Advisory record · `GHSA-8fcj-gf77-47mg`

- **Identifiers:** `GHSA-8fcj-gf77-47mg` · `CVE-2022-43756` · `GO-2023-1515`
- **State:** Confirmed
- **Severity:** CVSS 5.9 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-74](https://cwe.mitre.org/data/definitions/74.html)
- **Tags:** [Other injection](https://agentprime.io/advisories/tag/injection.md)
- **Published:** 14 Feb 2023
- **Updated:** 20 May 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 14 Feb 2023, 16:19 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/rancher/wrangler` (Go): affected `<0.7.4-security1 || >=0.8.0, <0.8.5-security1 || >=0.8.6, <0.8.11 || >=1.0.0, <1.0.1`; fixed in `0.7.4-security1`, `0.8.5-security1`, `0.8.11`, `1.0.1`

## Machine-written summary

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

> Wrangler (github.com/rancher/wrangler) versions before 0.7.4-security1, from 0.8.0 before 0.8.5-security1, from 0.8.6 before 0.8.11, and from 1.0.0 before 1.0.1 are affected. An attacker who can supply specially crafted Git credentials to an application using the Git package can exhaust its memory and CPU, causing a denial of service; the issue is triggered when accessing both private and public repositories. Upgrade to 0.7.4-security1, 0.8.5-security1, 0.8.11, 1.0.1, or later. Sanitizing input passed to the Git package to remove unsafe and ambiguous characters is a possible workaround.

Written 10 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.9 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H`, from CNA (suse)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0070, the 53rd percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 14 Feb 2023. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-8fcj-gf77-47mg](https://github.com/advisories/GHSA-8fcj-gf77-47mg)
- [OSV: GHSA-8fcj-gf77-47mg](https://osv.dev/vulnerability/GHSA-8fcj-gf77-47mg)
- <https://github.com/rancher/wrangler/commit/341018c8fef3e12867c7cb2649bd2cecac75f287>
- <https://github.com/advisories/GHSA-8fcj-gf77-47mg>
- <https://github.com/rancher/rancher/security/policy>

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-8fcj-gf77-47mg>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-8fcj-gf77-47mg/>. Everything for agents: <https://agentprime.io/llms.txt>.
