# CVE-2026-7150: dh1011 auto-favicon MCP Tool server.py generate_favicon_from_url server-side request forgery

> Remote attackers can exploit a server-side request forgery vulnerability in the auto-favicon MCP tool to access internal resources or bypass security controls.

- **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:P`)
- **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:** 27 Apr 2026
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-vmh7-9c7h-2pgg, PYSEC-2026-2386

## What is CVE-2026-7150?

CVE-2026-7150 is a medium-severity server-side request forgery vulnerability in dh1011 auto-favicon, published on 27 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in dh1011 auto-favicon up to f189116a9259950c2393f114dbcb94dde0ad864b. This issue affects the function generate_favicon_from_url of the file src/auto_favicon/server.py of the component MCP Tool. The manipulation of the argument image_url results in server-side request forgery. The attack may be performed from remote. The exploit has been made public and could be used. This product utilizes a rolling release system for continuous delivery, and as such, version information for affected or updated releases is not disclosed. 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-7150?

3 open source packages ship an affected version, including auto-favicon.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `auto-favicon` | PyPI | All versions to 1.0.1 | None |
| `auto-favicon` | PyPI | All versions to 1.0.1 | None |
| `auto-favicon` | PyPI | All versions to 1.0.1 | None |

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

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

## Is CVE-2026-7150 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7150 is a medium-severity server-side request forgery vulnerability in dh1011 auto-favicon, published on 27 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7150 exists.

Affected packages and fixed versions:
- auto-favicon (PyPI): affected all versions up to 1.0.1; no fix listed
- auto-favicon (PyPI): affected all versions up to 1.0.1; no fix listed
- auto-favicon (PyPI): affected all versions up to 1.0.1; no fix listed

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-7150/ (Markdown: https://insights.sbomify.com/CVE-2026-7150/index.md)
```

## Sources

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

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