CVE-2026-2558
Received Received - Intake
Server-Side Request Forgery in GeekAI Download Function

Publication date: 2026-02-16

Last updated on: 2026-04-29

Assigner: VulDB

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-16
Last Modified
2026-04-29
Generated
2026-05-07
AI Q&A
2026-02-16
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 3 associated CPEs
Vendor Product Version / Range
geekai geekai to 4.2.4 (inc)
geekai geekai 4.2.3
geekai geekai 4.2.4
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2026-2558 is a server-side request forgery (SSRF) vulnerability found in GeekAI versions up to 4.2.4, specifically in the Download function within the file api/handler/net_handler.go.

The vulnerability occurs because the function accepts a URL argument from the user without any validation or authentication and directly uses it to make HTTP requests.

This allows an attacker to manipulate the URL parameter to make the server send requests to unintended destinations, potentially accessing internal services or sensitive resources.

The vulnerability can be exploited remotely without authentication, and a proof-of-concept exploit is publicly available.


How can this vulnerability impact me? :

This vulnerability can impact you by allowing attackers to make the vulnerable server send arbitrary HTTP requests to internal or external systems.

Such unauthorized requests can lead to exposure of internal network services, unauthorized data access, or data exfiltration.

Attackers might access sensitive backend API ports or cloud metadata services, which can compromise the confidentiality, integrity, and availability of your system.

Because the server trusts user input without validation, it can be manipulated to perform SSRF attacks remotely without authentication.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

[{'type': 'paragraph', 'content': 'This vulnerability can be detected by monitoring requests to the `/api/download` endpoint that include a URL parameter without proper validation. You can look for unusual or unexpected outbound HTTP requests originating from the server to internal IP addresses or cloud metadata endpoints, which may indicate exploitation attempts.'}, {'type': 'paragraph', 'content': 'To detect exploitation attempts, you can use network monitoring tools or logs to identify HTTP GET requests made by the server to suspicious or internal URLs.'}, {'type': 'paragraph', 'content': 'Suggested commands to help detect this vulnerability include:'}, {'type': 'list_item', 'content': "Using curl or wget to test the endpoint with a crafted URL parameter, for example: `curl 'http://<target-server>/api/download?url=http://169.254.169.254/latest/meta-data/'` to check if the server fetches internal cloud metadata."}, {'type': 'list_item', 'content': 'Using network monitoring tools like tcpdump or Wireshark to capture outbound HTTP requests from the server: `tcpdump -i eth0 host <target-server-ip> and port 80`.'}, {'type': 'list_item', 'content': 'Checking server logs for requests to `/api/download` with URL parameters pointing to internal IP ranges (e.g., 10.0.0.0/8, 192.168.0.0/16).'}] [2, 3]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include implementing authentication and authorization checks on the `/api/download` endpoint to prevent unauthorized access.

Additionally, enforce strict validation of the URL parameter by implementing a whitelist of allowed URLs or domains to prevent arbitrary requests.

Blocking requests to internal IP addresses and cloud metadata service endpoints is also recommended to reduce the risk of SSRF exploitation.

Since no official patch or response has been provided by the GeekAI project, consider replacing the affected component with an alternative product or disabling the vulnerable functionality until a fix is available.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart