Flowise versions prior to 3.1.3 contain a Server-Side Request Forgery (SSRF) vulnerability due to improper normalization of IPv4-mapped IPv6 addresses in its HTTP security module. This allows attackers controlling DNS resolution to bypass IP deny lists and make requests to localhost, internal services, or cloud metadata endpoints. The issue is fixed in version 3.1.3.
OPeNDAP Hyrax contains a Server Side Request Forgery (SSRF) vulnerability that allows attackers to bypass allowed hosts restrictions via unvalidated HTTP redirects. This can cause the application to communicate with unauthorized internal or external systems. Additionally, user authentication headers, including a legacy Echo-Token credential, may be leaked to attacker-controlled endpoints during these redirects. Exploitation could enable unauthenticated attackers to access internal services and disclose credentials of authenticated users. A fix addressing these issues was released in Hyrax version 1.18.0. Until patched, administrators are advised to restrict gateway exposure to trusted networks.
A Server-Side Request Forgery (SSRF) vulnerability exists in the Visualizer WordPress plugin before version 4.0.6. This flaw allows users with Contributor-level access or higher to supply URLs that are fetched server-side without restriction to safe address ranges. The vulnerability enables attackers to perform SSRF against link-local instance metadata endpoints, retrieving cloud instance metadata including IAM credentials. The attack is non-blind, as the fetched response is returned in the reply.
EmbedPress WordPress plugin versions before 4.6.1 contain a Server-Side Request Forgery (SSRF) vulnerability. This flaw allows unauthenticated attackers to make the site send HTTP requests to internal hosts and services by exploiting unauthenticated endpoints that do not validate user-supplied URLs. The vulnerability bypasses WordPress core URL validation, resulting in a blind SSRF scenario.
The Simple Google Calendar Outlook Events Widget WordPress plugin before version 3.1.0 contains a Server-Side Request Forgery (SSRF) vulnerability. This flaw allows unauthenticated attackers to supply a URL that the plugin does not validate before making a server-side request. In some cases, attackers may read the response from the internal request. The vulnerability has a medium severity rating with a CVSS score of 5.3.
Adobe Campaign Classic (ACC) is affected by a Server-Side Request Forgery (SSRF) vulnerability that could result in privilege escalation. Exploitation of this issue does not require user interaction. Scope is changed.
ip-address is a library for parsing and manipulating IPv4 and IPv6 addresses in JavaScript. From 10.1.1 until 10.2.2, every special-use classification method is built on isInSubnet, which short-circuits to false whenever the address's own subnet mask is shorter than the reference range's mask. That mask comes verbatim from the CIDR suffix on the parsed input, so appending a suffix such as /0 suppresses classification entirely: isLoopback(), isPrivate(), isLinkLocal(), isCGNAT(), isMulticast(), isUnspecified(), isBroadcast(), isULA(), and getType() all report an internal address as unremarkable, while correctForm() and address still return the real internal target. An application that builds a network trust-boundary decision on these checks, for example a filter intended to block Server-Side Request Forgery, or SSRF, may therefore treat an internal target as external and allow the request. The underlying bit comparison is correct, and mask(n) already returns the first n bits of the full parsed address independently of subnetMask; the defect is solely that the containment guard sits in the classification path. This issue is fixed in version 10.2.2.
The ip-address JavaScript library prior to version 10.3.1 improperly validates input when parsing IPv4 addresses with octets that have leading zeros. This causes a mismatch between the library's interpretation and standard network parsers, potentially leading to incorrect classification of internal versus external IP addresses. This can affect security decisions such as Server-Side Request Forgery (SSRF) protections. The issue is fixed in version 10.3.1.
CTI-Transmute is affected by a server-side request forgery vulnerability in the evaluation report PDF-generation functionality.
User-controlled CTI content, including conversion names, descriptions, and comments, is converted from Markdown to HTML and rendered as a PDF using WeasyPrint. Before the patch, the renderer used WeasyPrint’s default URL-fetching behavior without restricting the protocols or destinations that could be referenced by the generated HTML.
An attacker able to supply content included in an evaluation report could inject crafted resource references using schemes such as http://, https://, or file://. When the report was rendered, CTI-Transmute could fetch these resources using the application server’s network connectivity and filesystem privileges.
Successful exploitation could allow an attacker to:
* access services available only from the CTI-Transmute server or its internal network;
* probe internal hosts and service endpoints;
* retrieve local files readable by the application process; and
* expose fetched content through the generated PDF, depending on the referenced resource type and rendering context.
The vulnerability is corrected by providing WeasyPrint with a restrictive URL fetcher that permits only self-contained data: URIs. The externally hosted Google Fonts stylesheet was also removed so that PDF generation performs no intentional network or filesystem fetches.
The Pixelavo WordPress plugin before 1.5.4 registers an unauthenticated AJAX action, gated only by a nonce that it emits publicly on every front-end page, that forwards client-supplied event data to the configured Facebook Conversions API using the administrator's stored access token. This allows an unauthenticated visitor to inject arbitrary conversion events into the administrator's Facebook ads account and exhaust the configured API quota.
vault-secrets-webhook is a Kubernetes mutating webhook that makes direct secret injection into Pods possible. Prior to 1.23.1, parseVaultConfig() in pkg/webhook/config.go accepts the vault.security.banzaicloud.io/vault-addr annotation, MutateConfigMap and MutateSecret call newVaultClient in pkg/webhook/webhook.go, and vault.security.banzaicloud.io/vault-serviceaccount can cause a ServiceAccount JWT to be sent to an attacker-controlled Vault address. This issue is fixed in version 1.23.1.
DSSRF is a Node.js library that provides a wide range of utilities and advanced SSRF defense checks. Prior to 1.0.5, is_url_safe can treat localhost as safe when DNS resolver 1.1.1.1 returns NXDOMAIN because dns.resolve4 yields no address and no dns.lookup fallback occurs, allowing server-side request forgery. This issue is fixed in version 1.0.5.
Server-Side Request Forgery in the PDF export component in maalfer Pentestify before 1.1.0 allows authenticated users to cause outbound HTTP GET requests from the server to arbitrary attacker-chosen destinations via unvalidated URLs stored in the finding images field or the report client_logo field, which the server-side headless browser fetches while rendering the report.
CVE-2026-14540 is a Server-Side Request Forgery (SSRF) vulnerability in Google mcp-toolbox versions 0.3.0 through 1.4.0. The vulnerability arises because the HTTP client used by the toolbox does not enforce restrictive redirect policies or validate target IPs, allowing attackers to manipulate redirections. This can cause the toolbox to make unauthorized requests to internal or arbitrary external endpoints. The vulnerability has a high severity score of 8. No official patch or remediation guidance is currently available.
A Server-Side Request Forgery (SSRF) in the xxl-job-admin/jobinfo/trigger component of xxl-job v3.4.0 allows authenticated attackers to scan resources via supplying a crafted HTTP request.
CVE-2026-67530 is a Server-Side Request Forgery (SSRF) vulnerability in ArnasDon's wacrm product, a self-hostable CRM template for WhatsApp. Versions 0.7.0 and earlier allow an authenticated user with automation privileges to submit arbitrary webhook URLs that the server fetches without proper SSRF protections. This enables requests to internal network addresses, including private, loopback, link-local, and cloud metadata endpoints such as 169.254.169.254. The vulnerability has been fixed in a later commit.
MaxKB is an open-source AI assistant for enterprise. In versions 2.0.0 through 2.10.4-lts, UpdateStoreTool.update_tool passes caller-supplied download_url and download_callback_url values to requests.get without equivalent trusted-host and redirect validation, allowing an authenticated workspace user to make the server request internal, loopback, link-local, or cloud metadata URLs. A fix is present on the v2 branch but has not yet been included in a published release.
Server-Side Request Forgery vulnerability in malach-it Boruta allows an unauthenticated remote attacker to cause the OAuth/OpenID authorization server to issue outbound HTTP requests to attacker-chosen URIs, including internal services and cloud metadata endpoints.
Three code paths fetch remote URIs supplied by the requester without sufficient validation of the target. Boruta.Oauth.Request.Base.fetch_unsigned_request/1 in lib/boruta/oauth/request/base.ex dereferences the OAuth request_uri parameter from the authorization request via Finch.build(:get, request_uri) |> Finch.request(OpenIDHttpClient). Boruta.Openid.parse_registration_params/2 in lib/boruta/openid.ex dereferences the jwks_uri supplied in an OpenID Connect dynamic client registration request. Boruta.Ecto.Clients.refresh_jwk_from_jwks_uri/1 in lib/boruta/adapters/ecto/clients.ex later refreshes the stored jwks_uri for an existing client. In all three paths the only validation is that the URI parses with a scheme (and one of the two request_uri clauses does not even restrict the scheme to http or https). The implementations do not require HTTPS, do not enforce a host or IP allowlist, do not reject loopback, private, link-local, or other non-public ranges after DNS resolution, do not cap response size, and do not constrain redirects. An attacker can therefore steer the server's HTTP client at arbitrary network targets reachable from the Boruta host.
This issue affects boruta: from 2.3.2 before 2.3.7.
CVE-2026-18353 is a high-severity server-side request forgery (SSRF) vulnerability in Eclipse Foundation's Eclipse CSI - PIA version 0.4.0. The vulnerability arises from improper validation of the unverified 'iss' claim in a JWT token at the /v1/upload/sbom endpoint. Due to inconsistent parsing of URLs containing backslashes by Python's urlparse and the requests library, an attacker can bypass issuer allowlist checks and cause the server to make arbitrary network requests to attacker-controlled hosts.