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.
4931 vulnerabilities reference this CWE, most recent first.
GHSA-XFQR-CG7J-569J
Vulnerability from github – Published: 2026-03-25 21:30 – Updated: 2026-03-25 21:30IBM InfoSphere Information Server 11.7.0.0 through 11.7.1.6 is vulnerable to server-side request forgery (SSRF). This may allow an authenticated attacker to send unauthorized requests from the system, potentially leading to network enumeration or facilitating other attacks.
{
"affected": [],
"aliases": [
"CVE-2026-1015"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-03-25T21:16:28Z",
"severity": "MODERATE"
},
"details": "IBM InfoSphere Information Server 11.7.0.0 through 11.7.1.6 is vulnerable to server-side request forgery (SSRF). This may allow an authenticated attacker to send unauthorized requests from the system, potentially leading to network enumeration or facilitating other attacks.",
"id": "GHSA-xfqr-cg7j-569j",
"modified": "2026-03-25T21:30:36Z",
"published": "2026-03-25T21:30:36Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-1015"
},
{
"type": "WEB",
"url": "https://www.ibm.com/support/pages/node/7266740"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-XFXF-HVQM-H74G
Vulnerability from github – Published: 2026-07-23 12:32 – Updated: 2026-07-23 12:32Contributor Server Side Request Forgery (SSRF) in JetEngine <= 3.8.11 versions.
{
"affected": [],
"aliases": [
"CVE-2026-65467"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-07-23T12:18:39Z",
"severity": "MODERATE"
},
"details": "Contributor Server Side Request Forgery (SSRF) in JetEngine \u003c= 3.8.11 versions.",
"id": "GHSA-xfxf-hvqm-h74g",
"modified": "2026-07-23T12:32:28Z",
"published": "2026-07-23T12:32:28Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-65467"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/wordpress/plugin/jet-engine/vulnerability/wordpress-jetengine-plugin-3-8-11-server-side-request-forgery-ssrf-vulnerability?_s_id=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-XG5G-26X8-CVF4
Vulnerability from github – Published: 2026-07-24 21:17 – Updated: 2026-07-24 21:17Impact
A builder-level user can make Budibase issue server-side HTTP requests to loopback or private-network targets by using DNS rebinding against two outbound fetch paths that are still not pinned to the validated DNS answer.
The first path is OpenAPI query import. It validates the supplied hostname with the blacklist and then performs a separate raw fetch. A hostname that resolves to a public address during validation and to 127.0.0.1 during the request is accepted.
The second path is REST datasource/query execution. It calls the fixed fetchWithBlacklist() helper, but provides a custom undici fetchFn that installs a dispatcher. The helper passes a pinned Node agent, but undici uses the dispatcher and resolves the original hostname again at connection time. This defeats the DNS pinning added for the previous outbound fetch advisory.
Impact is authenticated SSRF from the Budibase server process. An attacker with the relevant builder/query privileges can reach loopback or private HTTP services that should be blocked by Budibase's outbound fetch protections, subject to the normal response handling of each feature.
Reproduction
- Configure an attacker-controlled hostname so the validation lookup returns a public IP address and the later request lookup returns an internal address such as
127.0.0.1. - Start a loopback canary HTTP service on the Budibase host.
- For OpenAPI query import, submit an import URL such as
http://rebind.test:<port>/openapi.jsonthrough the builder query import endpoints. In a harness matching the current import code, validation resolvedrebind.testto8.8.8.8, the raw fetch then resolvedrebind.testto127.0.0.1, and the loopback canary returnedloopback-canary-hit:/openapi.json. - For REST datasource/query execution, configure a REST datasource/query URL using the same rebinding hostname. In a harness matching the current helper plus REST undici custom fetch path, a direct loopback URL was blocked and a pinned Node-agent control did not hit loopback, but the REST undici path re-resolved the hostname to
127.0.0.1and returnedREST-UNDICI-REBIND-CANARYfrom the loopback service.
Observed OpenAPI import proof:
{
"outcome": "allowed",
"body": "loopback-canary-hit:/openapi.json",
"lookups": [
{"phase": "guard", "hostname": "rebind.test", "address": "8.8.8.8"},
{"phase": "fetch", "hostname": "rebind.test", "address": "127.0.0.1"}
]
}
Observed REST undici proof:
{
"directControl": {"outcome": "blocked", "hitsAfter": 0},
"pinnedNodeFetchControl": {"outcome": "no_loopback_hit", "hitsAfter": 0},
"undiciBypass": {
"outcome": "allowed",
"status": 200,
"body": "REST-UNDICI-REBIND-CANARY",
"hitsAfter": 1
},
"lookupTrace": [
{"phase": "guard", "hostname": "rebind.test", "address": "8.8.8.8"},
{"phase": "fetch", "hostname": "rebind.test", "address": "127.0.0.1"}
]
}
Root cause and technical details
The central helper now resolves and validates the target hostname, then passes a pinned Node http.Agent or https.Agent to the request. That protects callers whose HTTP client honors the Node agent option.
OpenAPI query import does not use that helper. In packages/server/src/api/controllers/query/import/index.ts, assertUrlIsSafe() calls blacklist.isBlacklisted(parsed.hostname), but fetchFromUrl() then calls fetch(currentUrl, { redirect: "manual" }). That creates a validate-then-fetch gap where DNS can change between the blacklist lookup and the actual connection.
REST datasource/query execution uses the helper but changes the transport semantics. In packages/server/src/integrations/rest.ts, setDispatcher() creates an undici dispatcher with getDispatcher({ rejectUnauthorized, url: requestUrl }), then the custom fetch function calls fetch(requestUrl, setDispatcher(requestInput, requestUrl)). In packages/backend-core/src/utils/outboundFetch.ts, fetchWithBlacklist() passes the pinned Node agent to fetchFn, but undici fetch uses the supplied dispatcher instead. The actual connection performs a second hostname resolution and can be rebound to a blocked address.
Current affected code is present in latest master and in the latest release tag 3.39.14.
Remediation
Route OpenAPI query import through the pinned outbound fetch helper rather than validating and raw-fetching separately.
Make fetchWithBlacklist() pin the actual connection for every supported transport. For undici callers, provide a dispatcher whose lookup or connect behavior is pinned to the validated IP, or reject custom fetch functions that do not explicitly enforce the pinned address. Add regression coverage for direct loopback blocking, DNS rebinding through OpenAPI import, DNS rebinding through REST undici dispatcher, redirect-to-loopback, IPv4-mapped IPv6, and mixed public/private DNS answers.
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "@budibase/server"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "3.38.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": true,
"github_reviewed_at": "2026-07-24T21:17:25Z",
"nvd_published_at": null,
"severity": "HIGH"
},
"details": "## Impact\n\nA builder-level user can make Budibase issue server-side HTTP requests to loopback or private-network targets by using DNS rebinding against two outbound fetch paths that are still not pinned to the validated DNS answer.\n\nThe first path is OpenAPI query import. It validates the supplied hostname with the blacklist and then performs a separate raw fetch. A hostname that resolves to a public address during validation and to `127.0.0.1` during the request is accepted.\n\nThe second path is REST datasource/query execution. It calls the fixed `fetchWithBlacklist()` helper, but provides a custom undici `fetchFn` that installs a `dispatcher`. The helper passes a pinned Node `agent`, but undici uses the dispatcher and resolves the original hostname again at connection time. This defeats the DNS pinning added for the previous outbound fetch advisory.\n\nImpact is authenticated SSRF from the Budibase server process. An attacker with the relevant builder/query privileges can reach loopback or private HTTP services that should be blocked by Budibase\u0027s outbound fetch protections, subject to the normal response handling of each feature.\n\n## Reproduction\n\n1. Configure an attacker-controlled hostname so the validation lookup returns a public IP address and the later request lookup returns an internal address such as `127.0.0.1`.\n2. Start a loopback canary HTTP service on the Budibase host.\n3. For OpenAPI query import, submit an import URL such as `http://rebind.test:\u003cport\u003e/openapi.json` through the builder query import endpoints. In a harness matching the current import code, validation resolved `rebind.test` to `8.8.8.8`, the raw fetch then resolved `rebind.test` to `127.0.0.1`, and the loopback canary returned `loopback-canary-hit:/openapi.json`.\n4. For REST datasource/query execution, configure a REST datasource/query URL using the same rebinding hostname. In a harness matching the current helper plus REST undici custom fetch path, a direct loopback URL was blocked and a pinned Node-agent control did not hit loopback, but the REST undici path re-resolved the hostname to `127.0.0.1` and returned `REST-UNDICI-REBIND-CANARY` from the loopback service.\n\nObserved OpenAPI import proof:\n\n```json\n{\n \"outcome\": \"allowed\",\n \"body\": \"loopback-canary-hit:/openapi.json\",\n \"lookups\": [\n {\"phase\": \"guard\", \"hostname\": \"rebind.test\", \"address\": \"8.8.8.8\"},\n {\"phase\": \"fetch\", \"hostname\": \"rebind.test\", \"address\": \"127.0.0.1\"}\n ]\n}\n```\n\nObserved REST undici proof:\n\n```json\n{\n \"directControl\": {\"outcome\": \"blocked\", \"hitsAfter\": 0},\n \"pinnedNodeFetchControl\": {\"outcome\": \"no_loopback_hit\", \"hitsAfter\": 0},\n \"undiciBypass\": {\n \"outcome\": \"allowed\",\n \"status\": 200,\n \"body\": \"REST-UNDICI-REBIND-CANARY\",\n \"hitsAfter\": 1\n },\n \"lookupTrace\": [\n {\"phase\": \"guard\", \"hostname\": \"rebind.test\", \"address\": \"8.8.8.8\"},\n {\"phase\": \"fetch\", \"hostname\": \"rebind.test\", \"address\": \"127.0.0.1\"}\n ]\n}\n```\n\n## Root cause and technical details\n\nThe central helper now resolves and validates the target hostname, then passes a pinned Node `http.Agent` or `https.Agent` to the request. That protects callers whose HTTP client honors the Node `agent` option.\n\nOpenAPI query import does not use that helper. In `packages/server/src/api/controllers/query/import/index.ts`, `assertUrlIsSafe()` calls `blacklist.isBlacklisted(parsed.hostname)`, but `fetchFromUrl()` then calls `fetch(currentUrl, { redirect: \"manual\" })`. That creates a validate-then-fetch gap where DNS can change between the blacklist lookup and the actual connection.\n\nREST datasource/query execution uses the helper but changes the transport semantics. In `packages/server/src/integrations/rest.ts`, `setDispatcher()` creates an undici dispatcher with `getDispatcher({ rejectUnauthorized, url: requestUrl })`, then the custom fetch function calls `fetch(requestUrl, setDispatcher(requestInput, requestUrl))`. In `packages/backend-core/src/utils/outboundFetch.ts`, `fetchWithBlacklist()` passes the pinned Node `agent` to `fetchFn`, but undici fetch uses the supplied `dispatcher` instead. The actual connection performs a second hostname resolution and can be rebound to a blocked address.\n\nCurrent affected code is present in latest `master` and in the latest release tag `3.39.14`.\n\n## Remediation\n\nRoute OpenAPI query import through the pinned outbound fetch helper rather than validating and raw-fetching separately.\n\nMake `fetchWithBlacklist()` pin the actual connection for every supported transport. For undici callers, provide a dispatcher whose lookup or connect behavior is pinned to the validated IP, or reject custom fetch functions that do not explicitly enforce the pinned address. Add regression coverage for direct loopback blocking, DNS rebinding through OpenAPI import, DNS rebinding through REST undici dispatcher, redirect-to-loopback, IPv4-mapped IPv6, and mixed public/private DNS answers.",
"id": "GHSA-xg5g-26x8-cvf4",
"modified": "2026-07-24T21:17:25Z",
"published": "2026-07-24T21:17:25Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/Budibase/budibase/security/advisories/GHSA-xg5g-26x8-cvf4"
},
{
"type": "WEB",
"url": "https://github.com/Budibase/budibase/pull/19178"
},
{
"type": "WEB",
"url": "https://github.com/Budibase/budibase/commit/1fecb3fc3497e8db7b60b42cc514ce304ffe3a41"
},
{
"type": "WEB",
"url": "https://github.com/Budibase/budibase/commit/5758bdb242802ca20c4ed0dc579e4330ee898ef3"
},
{
"type": "WEB",
"url": "https://github.com/Budibase/budibase/commit/586802b5706367520d14245e18a7d0cabab0be11"
},
{
"type": "PACKAGE",
"url": "https://github.com/Budibase/budibase"
},
{
"type": "WEB",
"url": "https://github.com/Budibase/budibase/releases/tag/3.39.30"
}
],
"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"
}
],
"summary": " Budibase: DNS rebinding SSRF bypasses remain in OpenAPI import and REST query execution"
}
GHSA-XG73-5HQJ-7HWG
Vulnerability from github – Published: 2025-08-09 21:30 – Updated: 2025-08-09 21:30A vulnerability, which was classified as problematic, has been found in Vinades NukeViet up to 4.5.06. This issue affects some unknown processing of the file /admin/index.php?language=en&nv=upload of the component Module Handler. The manipulation leads to server-side request forgery. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
{
"affected": [],
"aliases": [
"CVE-2025-8772"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-08-09T20:15:25Z",
"severity": "MODERATE"
},
"details": "A vulnerability, which was classified as problematic, has been found in Vinades NukeViet up to 4.5.06. This issue affects some unknown processing of the file /admin/index.php?language=en\u0026nv=upload of the component Module Handler. The manipulation leads to server-side request forgery. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.",
"id": "GHSA-xg73-5hqj-7hwg",
"modified": "2025-08-09T21:30:23Z",
"published": "2025-08-09T21:30:22Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-8772"
},
{
"type": "WEB",
"url": "https://hkohi.ca/vulnerability/19"
},
{
"type": "WEB",
"url": "https://vuldb.com/?ctiid.319295"
},
{
"type": "WEB",
"url": "https://vuldb.com/?id.319295"
},
{
"type": "WEB",
"url": "https://vuldb.com/?submit.624976"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/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-XG77-2M7H-4885
Vulnerability from github – Published: 2025-05-27 18:30 – Updated: 2025-05-29 21:31maccms10 v2025.1000.4047 is vulnerable to Server-Side request forgery (SSRF) in Friend Link Management.
{
"affected": [],
"aliases": [
"CVE-2025-45475"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-05-27T18:15:31Z",
"severity": "MODERATE"
},
"details": "maccms10 v2025.1000.4047 is vulnerable to Server-Side request forgery (SSRF) in Friend Link Management.",
"id": "GHSA-xg77-2m7h-4885",
"modified": "2025-05-29T21:31:37Z",
"published": "2025-05-27T18:30:51Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-45475"
},
{
"type": "WEB",
"url": "https://www.yuque.com/morysummer/vx41bz/dzidfm8vn2h5k1lb"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L",
"type": "CVSS_V3"
}
]
}
GHSA-XG8C-MW7J-WCV9
Vulnerability from github – Published: 2022-05-24 19:14 – Updated: 2022-05-24 19:14On version 16.0.x before 16.0.1.2, insufficient permission checks may allow authenticated users with guest privileges to perform Server-Side Request Forgery (SSRF) attacks through F5 Advanced Web Application Firewall (WAF) and the BIG-IP ASM Configuration utility. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
{
"affected": [],
"aliases": [
"CVE-2021-23029"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-09-14T23:15:00Z",
"severity": "HIGH"
},
"details": "On version 16.0.x before 16.0.1.2, insufficient permission checks may allow authenticated users with guest privileges to perform Server-Side Request Forgery (SSRF) attacks through F5 Advanced Web Application Firewall (WAF) and the BIG-IP ASM Configuration utility. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.",
"id": "GHSA-xg8c-mw7j-wcv9",
"modified": "2022-05-24T19:14:48Z",
"published": "2022-05-24T19:14:48Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-23029"
},
{
"type": "WEB",
"url": "https://support.f5.com/csp/article/K52420610"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-XG93-7QJ8-C5VG
Vulnerability from github – Published: 2023-06-08 21:30 – Updated: 2024-04-04 04:40An issue in Chamilo v1.11.* up to v1.11.18 allows attackers to execute a Server-Side Request Forgery (SSRF) and obtain information on the services running on the server via crafted requests in the social and links tools.
{
"affected": [],
"aliases": [
"CVE-2023-34959"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-06-08T19:15:10Z",
"severity": "MODERATE"
},
"details": "An issue in Chamilo v1.11.* up to v1.11.18 allows attackers to execute a Server-Side Request Forgery (SSRF) and obtain information on the services running on the server via crafted requests in the social and links tools.",
"id": "GHSA-xg93-7qj8-c5vg",
"modified": "2024-04-04T04:40:47Z",
"published": "2023-06-08T21:30:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-34959"
},
{
"type": "WEB",
"url": "https://github.com/chamilo/chamilo-lms/commit/cc278f01864948b1fb160e03f0a3dc0875d5f81f"
},
{
"type": "WEB",
"url": "https://github.com/chamilo/chamilo-lms/commit/ea5791ff8ce6ea45148a171b0da5348a7c415e6f"
},
{
"type": "WEB",
"url": "https://github.com/chamilo/chamilo-lms/commit/ed946908fef23e8aa4cefc28f745f3cd6710099f"
},
{
"type": "WEB",
"url": "https://support.chamilo.org/projects/1/wiki/Security_issues#Issue-111-2023-04-20-Moderate-impact-Low-risk-Multiple-blind-SSRF-in-links-and-social-tools"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-XGC5-WM9V-RQR3
Vulnerability from github – Published: 2024-12-13 15:30 – Updated: 2026-04-01 18:32Server-Side Request Forgery (SSRF) vulnerability in Hep Hep Hurra (HHH) Hurrakify allows Server Side Request Forgery.This issue affects Hurrakify: from n/a through 2.4.
{
"affected": [],
"aliases": [
"CVE-2024-54330"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-12-13T15:15:40Z",
"severity": "HIGH"
},
"details": "Server-Side Request Forgery (SSRF) vulnerability in Hep Hep Hurra (HHH) Hurrakify allows Server Side Request Forgery.This issue affects Hurrakify: from n/a through 2.4.",
"id": "GHSA-xgc5-wm9v-rqr3",
"modified": "2026-04-01T18:32:46Z",
"published": "2024-12-13T15:30:45Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-54330"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/wordpress/plugin/hurrakify/vulnerability/wordpress-hurrakify-plugin-2-4-server-side-request-forgery-ssrf-vulnerability?_s_id=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-XGCH-X3MX-CM3C
Vulnerability from github – Published: 2026-07-15 21:58 – Updated: 2026-07-15 21:58The privateNetworks blocklist was found to be missing newly added CIDR ranges. More specifically, the following CIDR ranges were not being blocked:
- 64:ff9b:1::/48: NAT64 local-use prefix (RFC 8215)
- 5f00::/16: Segment Routing (SRv6) SIDs (RFC 9602)
- 3fff::/20: documentation prefix (RFC 9637)
- 100:0:0:1::/64: Dummy IPv6 Prefix (RFC 9780)
Impact
If exploited, an attacker would potentially be able to reach resources hosted on the IPs residing in the missing ranges.
Workarounds
Disable IPv6 by setting EnableIPv6(false). This is the default behavior of the library.
Resolution
Upgrade to v0.2.4
Credits
safeurl thanks @tonghuaroot for reporting.
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "github.com/doyensec/safeurl"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.2.4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-54452"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": true,
"github_reviewed_at": "2026-07-15T21:58:03Z",
"nvd_published_at": null,
"severity": "MODERATE"
},
"details": "The `privateNetworks` blocklist was found to be missing newly added CIDR ranges. More specifically, the following CIDR ranges were not being blocked:\n- `64:ff9b:1::/48`: NAT64 local-use prefix (RFC 8215)\n- `5f00::/16`: Segment Routing (SRv6) SIDs (RFC 9602)\n- `3fff::/20`: documentation prefix (RFC 9637)\n- `100:0:0:1::/64`: Dummy IPv6 Prefix (RFC 9780)\n\n### Impact\nIf exploited, an attacker would potentially be able to reach resources hosted on the IPs residing in the missing ranges.\n\n### Workarounds\nDisable IPv6 by setting `EnableIPv6(false)`. This is the default behavior of the library.\n\n### Resolution\nUpgrade to v0.2.4\n\n### Credits\nsafeurl thanks @tonghuaroot for reporting.",
"id": "GHSA-xgch-x3mx-cm3c",
"modified": "2026-07-15T21:58:03Z",
"published": "2026-07-15T21:58:03Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/doyensec/safeurl/security/advisories/GHSA-xgch-x3mx-cm3c"
},
{
"type": "PACKAGE",
"url": "https://github.com/doyensec/safeurl"
},
{
"type": "WEB",
"url": "https://github.com/doyensec/safeurl/releases/tag/v0.2.4"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "safeurl is Missing IPv6 CIDR Ranges in Blocklist"
}
GHSA-XGG8-FF2M-M77X
Vulnerability from github – Published: 2025-06-30 21:30 – Updated: 2025-06-30 21:30Akamai CloudTest before 60 2025.06.09 (12989) allows SSRF.
{
"affected": [],
"aliases": [
"CVE-2025-52491"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-06-30T20:15:25Z",
"severity": "MODERATE"
},
"details": "Akamai CloudTest before 60 2025.06.09 (12989) allows SSRF.",
"id": "GHSA-xgg8-ff2m-m77x",
"modified": "2025-06-30T21:30:53Z",
"published": "2025-06-30T21:30:53Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-52491"
},
{
"type": "WEB",
"url": "https://techdocs.akamai.com/cloudtest/changelog/june-9-2025-enhancements-and-bug-fixes"
},
{
"type": "WEB",
"url": "https://www.akamai.com/products/cloudtest"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/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.