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

CVE-2026-2558

MEDIUM · 6.3 CVSS v3.1 Published 2026-02-16
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 flaw has been found in GeekAI up to 4.2.4. The affected element is the function Download of the file api/handler/net_handler.go. This manipulation of the argument url causes server-side request forgery. Remote exploitation of the attack is possible. The exploit has been published and may be used. 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 · high confidence

This is a Server-Side Request Forgery (SSRF) vulnerability in GeekAI up to version 4.2.4. The Download function in api/handler/net_handler.go accepts a user-controlled URL parameter without proper validation, allowing attackers to induce the server to make requests to arbitrary internal or external URLs.

MitigationImplement strict URL validation and allowlisting for the url parameter to restrict requests to trusted domains or IP ranges. Additionally, disable or restrict outbound network requests from the vulnerable endpoint.

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 GeekAI installation and identify version
    Search for GeekAI installation directories or check the application's version file/config. Common locations may include /opt/geekai, the application root directory, or check for a version indicator in the application startup logs or config file.
    Affected if GeekAI is installed and the version is 4.2.4 or lower
  2. Verify the vulnerable file exists
    Check for the presence of api/handler/net_handler.go in the GeekAI installation directory. This file contains the Download function that handles the URL parameter.
    Affected if The file api/handler/net_handler.go exists and contains a Download function that processes a url parameter
  3. Confirm the Download endpoint is accessible
    Identify if there is an API route that maps to the Download function in net_handler.go. Check the application's routing configuration or API documentation to determine the endpoint path (typically under /api/).
    Affected if An API endpoint for the Download function is exposed and accessible to users
  4. Test if URL parameter lacks validation
    Inspect the source code of net_handler.go to see if the url parameter is validated before being used in an HTTP request. Look for allowlists, validation logic, or sanitization functions before the request is made.
    Affected if The code accepts a user-supplied URL without proper validation or allowlisting logic, or no validation is found in the function
  5. Check network exposure
    Determine if the server can make outbound HTTP requests. This is inherent to the vulnerability but check if the application has any network restrictions configured.
    Affected if The server has the ability to make outbound HTTP requests (default condition for this SSRF to be exploitable)

A user is affected if they are running GeekAI version 4.2.4 or lower with the Download function in api/handler/net_handler.go exposed and accessible, where the url parameter is not validated before use in server-side requests.

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 URL validation and allowlisting for the url parameter to restrict requests to trusted domains or IP ranges. Additionally, disable or restrict outbound network requests from the vulnerable endpoint.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2558 — 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-2558 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