# CVE-2026-74858: jae-jae fetcher-mcp URL Validation security-credentials fetch_urls server-side request forgery

> A server-side request forgery vulnerability in the fetcher-mcp library allows attackers to access internal metadata endpoints, potentially exposing sensitive credentials.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** GHSA-c33j-cj33-6649

## What is CVE-2026-74858?

CVE-2026-74858 is a medium-severity server-side request forgery vulnerability in jae-jae fetcher-mcp, published on 17 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability has been found in jae-jae fetcher-mcp up to 0.3.9. Impacted is the function fetch_url/fetch_urls of the file /latest/meta-data/iam/security-credentials/ of the component URL Validation. Such manipulation leads to server-side request forgery. It is possible to launch the attack remotely. The project was informed of the problem early through an issue report but has not responded yet.

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

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


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

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

## Is CVE-2026-74858 being exploited?

There is no known exploitation of CVE-2026-74858 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74858 is a medium-severity server-side request forgery vulnerability in jae-jae fetcher-mcp, published on 17 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-74858 in the wild and no public exploit code.

Affected product: jae-jae fetcher-mcp. 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-74858/ (Markdown: https://insights.sbomify.com/CVE-2026-74858/index.md)
```

## Sources

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

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