# CVE-2026-82289: Gitingest Prefix-Based Git Host Check Enables Request Forgery and Token Disclosure

> Attackers can exploit hostname validation flaws to trigger server-side requests and disclose GitHub personal access tokens via basic authentication.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Aug 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-mvv9-5ggf-37rj

## What is CVE-2026-82289?

CVE-2026-82289 is a high-severity server-side request forgery vulnerability in coderamp-labs gitingest, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Gitingest through 0.3.1 fails to properly validate hostnames in _validate_host, accepting any host with a git., gitlab., or github. prefix regardless of known-hosts list membership. Attackers can submit URLs with attacker-controlled hostnames to trigger outbound connections to arbitrary hosts and disclose GitHub personal access tokens via HTTP basic credentials.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-82289 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82289 is a high-severity server-side request forgery vulnerability in coderamp-labs gitingest, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82289 exists.

Affected product: coderamp-labs gitingest. 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-82289/ (Markdown: https://insights.sbomify.com/CVE-2026-82289/index.md)
```

## Sources

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

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