dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-7150

MEDIUM · 6.3 CVSS v3.1 Published 2026-04-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a Server-Side Request Forgery (SSRF) vulnerability in the auto-favicon feature of the dh1011 project. The generate_favicon_from_url function in src/auto_favicon/server.py accepts user-controlled image_url input without proper validation, allowing remote attackers to make the server request arbitrary URLs and potentially access internal services or exfiltrate data.

MitigationImplement strict input validation and URL allow-listing for the image_url parameter. Restrict outbound network access from the server and consider network segmentation to limit SSRF impact on internal infrastructure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate dh1011 project installation
    Search for the dh1011 project directory or package in your environment. Common locations include: the source code repository, installed Python packages (pip list or pip show), or the application root directory.
    Affected if The dh1011 project is present in your environment.
  2. Verify auto_favicon module exists
    Check for the presence of src/auto_favicon/server.py file within the dh1011 project structure. This file contains the vulnerable function.
    Affected if The file src/auto_favicon/server.py exists in your installation.
  3. Identify generate_favicon_from_url function
    Open src/auto_favicon/server.py and search for the generate_favicon_from_url function definition. Confirm it accepts an image_url parameter.
    Affected if The generate_favicon_from_url function exists and accepts image_url input.
  4. Check input validation on image_url
    Review the generate_favicon_from_url function code to see if the image_url parameter undergoes any validation, sanitization, or allow-listing before being used in network requests.
    Affected if The image_url parameter lacks proper validation (no URL allow-listing, no scheme validation, no hostname restriction).
  5. Determine if auto-favicon feature is enabled
    Check your application configuration, routing, or exposed endpoints to see if the auto-favicon feature (typically an API endpoint) is enabled and accessible to users.
    Affected if The auto-favicon endpoint is enabled and accessible to untrusted users.
  6. Assess server network posture
    Review outbound network access controls, firewall rules, or network segmentation applied to the server running this application.
    Affected if The server can make arbitrary outbound network requests without restriction.

You are affected if dh1011 is installed, the auto_favicon/server.py module exists with generate_favicon_from_url function, and the image_url parameter lacks proper validation while the feature is exposed to users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and URL allow-listing for the image_url parameter. Restrict outbound network access from the server and consider network segmentation to limit SSRF impact on internal infrastructure.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7150 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7150 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data