CVE-2025-64522
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-11-10

Last updated on: 2025-12-31

Assigner: GitHub, Inc.

Description
Soft Serve is a self-hostable Git server for the command line. Versions prior to 0.11.1 have a SSRF vulnerability where webhook URLs are not validated, allowing repository administrators to create webhooks targeting internal services, private networks, and cloud metadata endpoints. Version 0.11.1 fixes the vulnerability.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-11-10
Last Modified
2025-12-31
Generated
2026-05-07
AI Q&A
2025-11-11
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
charm soft_serve to 0.11.1 (exc)
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?

This vulnerability is a Server-Side Request Forgery (SSRF) in Soft Serve versions prior to 0.11.1. It occurs because webhook URLs are not properly validated, allowing repository administrators to create webhooks that can target internal services, private networks, and cloud metadata endpoints. This can lead to unauthorized access or interaction with internal resources.


How can this vulnerability impact me? :

The vulnerability can allow an attacker with repository administrator privileges to make the server send requests to internal or private network services, potentially exposing sensitive information or enabling further attacks. It can lead to high confidentiality impact, limited integrity impact, and limited availability impact as indicated by the CVSS score.


What immediate steps should I take to mitigate this vulnerability?

Upgrade Soft Serve to version 0.11.1 or later, as this version fixes the SSRF vulnerability by validating webhook URLs. Additionally, review and restrict webhook configurations to prevent targeting internal services, private networks, or cloud metadata endpoints.


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