SSRF
Monthly
Server-side request forgery in Dradis Community Edition 5.1.0-5.2.0 allows any authenticated non-admin user to hijack the AI provider configuration and redirect server-initiated HTTP requests to arbitrary URLs, including internal cloud metadata endpoints such as 169.254.169.254. A broken authorization gate in ProvidersController and AgentsController is conditioned on the Ruby constant Dradis::Pro, which is never defined in CE builds, so the admin_required filter is silently skipped for all CE installations. Non-2xx responses from attacker-supplied URLs are reflected verbatim to the attacker's browser via ActionCable/Turbo Stream, enabling exfiltration of internal service content. No public exploit code or CISA KEV listing has been identified at time of analysis.
Server-side request forgery in Adobe Campaign Classic (ACC) escalates to arbitrary code execution in the context of the running user, giving an unauthenticated network attacker full control per Adobe's CVSS:3.1 base score of 10.0 (scope-changed). The flaw lets an attacker coerce the server into making attacker-controlled requests that pivot into code execution with no user interaction. No public exploit has been identified at time of analysis and the issue is not listed in CISA KEV; the only reference is an Adobe advisory (APSB26-134) served from an internal, non-public host and could not be independently verified.
Server-Side Request Forgery (SSRF) in JFrog Artifactory allows a low-privileged authenticated user with read access to a remote VCS repository to replace the repository's configured origin URL or supply an arbitrary absolute VCS data URL, causing Artifactory's server process to issue outbound HTTP requests to attacker-controlled destinations - including internal network services, cloud metadata endpoints, or other infrastructure inaccessible from the public internet. The scope-changed CVSS vector (S:C) confirms the impact extends beyond Artifactory itself to systems on its internal network segment. No public exploit identified at time of analysis, and this vulnerability is not listed in the CISA KEV catalog.
Server-Side Request Forgery in PraisonAI's Jobs API (pip/praisonai < 4.6.58) results from two compounding flaws: a fail-open DNS error handler in `JobSubmitRequest.validate_webhook_url()` that silently accepts any webhook URL when `socket.gaierror` is raised, and a TOCTOU race where `JobExecutor._send_webhook()` performs a completely independent DNS resolution via `httpx.AsyncClient` minutes to hours after validation. Authenticated attackers with a valid API bearer token can submit a job whose `webhook_url` hostname returns NXDOMAIN at validation time, then update DNS to a private IP before job completion, causing the executor to POST job result data to internal infrastructure. A detailed proof-of-concept is publicly available in GHSA-rg5q-pp8p-f7jm; no public exploit identified at time of analysis beyond the PoC, and this CVE is not listed in CISA KEV.
Server-Side Request Forgery in praisonaiagents (pip package, versions < 1.6.58) allows any attacker who can influence an AI agent's crawl target - via crafted task instructions or prompt injection embedded in previously crawled content - to exfiltrate cloud instance metadata (including IAM credentials), internal localhost services, and RFC1918 API endpoints. The web_crawl tool's SSRF protection validates only the initial URL's hostname IP, then invokes httpx with follow_redirects=True, allowing an attacker-controlled public URL to 302-redirect the agent to 169.254.169.254 or 127.0.0.1 without any re-validation. This is an incomplete fix for a prior SSRF class in the same component. A fully functional proof-of-concept is publicly documented in GHSA-5r34-2g38-6569, and no public exploit identified at time of analysis beyond the PoC; no CISA KEV listing is present.
Server-side request forgery in Ech0 before version 4.7.3 allows authenticated users to pivot through the application server to reach internal infrastructure, including cloud provider metadata APIs and Kubernetes service endpoints. The root cause is a missing URL-validation call: `fetchPeerConnectInfo` in `internal/service/connect/connect.go` invokes the unguarded `SendRequest` helper rather than the `SendSafeRequest` variant that enforces `ValidatePublicHTTPURL` private-IP blocking. A working proof-of-concept demonstrating AWS IMDSv1 and Kubernetes API enumeration is publicly available in the GHSA advisory; no active exploitation via CISA KEV has been confirmed, though the CVSS 4.0 score of 8.3 with SC:H reflects elevated impact potential for cloud-hosted deployments.
Server-side request forgery in Apache Hive versions 2.1.0 through 4.2.0 lets an authenticated user with CREATE TABLE rights coerce the HiveServer2/Metastore process into fetching an attacker-chosen URL by planting a crafted avro.schema.url table property on an Avro table that is later queried. The fetch runs with the Hive service identity, exposing cloud instance metadata (e.g. 169.254.169.254), internal-only network services, and local files. No public exploit is identified at time of analysis and EPSS is low (0.29%), but the CVSS 9.1 rating and low attack complexity make it a meaningful post-authentication risk; upgrade to 4.2.1 resolves it.
Server-side request forgery in NLTK before 3.10.3 allows unauthenticated remote attackers to reach internal HTTP services and load attacker-controlled downloader indexes when an HTTP proxy is configured. The flaw sits in nltk.pathsec.urlopen and its callers (nltk.data.load, nltk.downloader.Downloader.index, nltk.downloader.Downloader.download): local hostname validation passes the supplied public URL, but proxy-handler inheritance then replaces NLTK's safe URL handlers so the actual fetch is executed by the proxy against an internally-resolvable destination that is never re-validated. No public exploit code or CISA KEV listing has been identified at time of analysis; the CVSS 4.0 base score is 8.7, reflecting high confidentiality impact under network-accessible, unauthenticated conditions.
Server-side request forgery in Hi.Events (all versions prior to 1.11.1-beta) allows an authenticated platform user to exfiltrate responses from internal network services, including cloud metadata endpoints, by exploiting a time-of-check/time-of-use gap in webhook URL validation. The registration-time guard in NoInternalUrlRule is never repeated at dispatch, and Guzzle's default redirect-following allows a destination that answers with a redirect to a loopback or RFC-1918 address to cause the server to issue the secondary request. Critically, this is not blind SSRF: WebhookResponseHandlerService stores the response body and WebhookLogResource exposes it via the webhook logs API, enabling direct credential or secret exfiltration. No public exploit has been identified at time of analysis, and the CVE is not listed in CISA KEV.
SSRF vulnerabilities in AWX notification backends (webhook, Mattermost, Rocket.Chat, and Grafana) allow an authenticated organization notification administrator to cause the AWX control node to issue outbound HTTP requests to internal, loopback, or RFC-1918 addresses that are not externally reachable. Beyond basic SSRF, the webhook backend compounds the risk by following HTTP redirects and replaying configured Basic Authentication credentials to the redirect destination regardless of host change, enabling credential exfiltration to attacker-controlled endpoints; the Grafana backend similarly exposes its API key by forwarding the Authorization header verbatim to any configured target URL. No public exploit has been identified at time of analysis, but the Changed scope and high confidentiality impact in the CVSS vector reflect significant real-world risk given the network position AWX control nodes typically occupy.
PDF export in RansomLook allows authenticated analysts to read arbitrary server-side files and conduct server-side request forgery by embedding crafted resource references in analysis documents. Prior to the patch, WeasyPrint's default URL fetcher resolved any scheme - including file:// and http:// - using the privileges and network access of the RansomLook server process, enabling exfiltration of local configuration and credentials or enumeration of internal network services. No public exploit code or CISA KEV listing exists at time of analysis; a fix is confirmed via GitHub commit 34dc0285583dae483b4d48c8e98fff942b755f5f, which introduces a strict URL allowlist restricting rendering to data: URIs, the report logo, and analysis asset files.
Server-side request forgery in Hugo static site generator (versions 0.91.0 through 0.165.0) allows an attacker who can supply a URL through site content - via front-matter fields or a connected CMS - to silently fetch loopback, RFC 1918, or cloud-metadata endpoints during the build process, embedding the internal response directly into the published static output. The security.http.urls allowlist, Hugo's only guard on resources.GetRemote outbound fetches, evaluates hostname strings without performing DNS resolution, meaning any registered domain whose A record points to a private or metadata IP bypasses the policy entirely, and no dial-time hook in the HTTP client provides a second check. No public exploit code has been identified at time of analysis, but the attack requires only DNS control and content-write access, making it operationally straightforward in CI/CD-integrated deployments.
Server-side request forgery and address-policy bypass in fast-uri, the Node.js URI parser used widely in the fastify ecosystem, allows remote unauthenticated attackers to redirect outbound requests from a target application to local or private IPv6 addresses by submitting crafted bracketed IPv6 literals with invalid trailing characters. The custom IPv6 parser silently normalizes malformed literals - collapsing some to the unspecified address (loopback) and others to private-range addresses - and returns no error on the parsed result, defeating any application-level error checking. No public exploit code or CISA KEV listing has been identified at time of analysis, but the attack requires no special privileges and low complexity, making automated exploitation plausible against any exposed application that normalizes untrusted URLs through an affected fast-uri version.
Parsing and serialization inconsistency in fast-uri, the Node.js URI parser core to the Fastify ecosystem, allows network-accessible, unauthenticated attackers to supply percent-encoded slashes in the scheme component, causing the library to report host as undefined during parsing while serialization emits a network-path reference with an attacker-controlled authority. Applications that allowlist requests on the parsed host value, or that treat a no-authority parse result as safe to resolve against a base URI, are bypassed - enabling server-side request forgery, off-site redirects, and address-policy evasion. No public exploit has been identified at time of analysis, but the CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms exploitation requires no authentication and no special configuration, making affected deployments an immediate upgrade priority.
Double-decoding of percent-encoded hostnames in fast-uri (Node.js URI parser) creates a server-side request forgery and host-policy bypass primitive in versions 2.4.1-2.4.4, 3.1.2-3.1.5, and 4.0.0-4.1.2. The library decodes percent escapes once during hostname parsing and again during authority recomposition, so a single normalize or resolve call on a doubly-encoded input can silently resolve to a different network destination - including loopback addresses - than the encoded form represents. Any application layer sitting fast-uri in front of outbound routing guards, redirect allow-lists, or host-policy checks is therefore vulnerable to SSRF. This is an incomplete-fix variant of CVE-2026-6322; no public exploit code or active exploitation (CISA KEV) has been identified at time of analysis.
Server-Side Request Forgery in the Mailgun for WordPress plugin (versions up to and including 2.2.0) lets unauthenticated attackers coerce the WordPress server into making authenticated requests to arbitrary Mailgun API endpoints using the site's own stored API key. Because the add_list() function trusts user-controlled array keys from $_POST['addresses'] and only runs them through sanitize_text_field(), an attacker can path-traverse to any Mailgun endpoint - notably creating inbound email-forwarding routes to intercept password-reset messages and take over the administrator account. Reported by Wordfence with a CVSS of 9.8; no public exploit identified at time of analysis and no CISA KEV listing.
Server-side request forgery in Microsoft's Azure SQL Database cloud service lets an unauthorized network attacker coerce the service into making backend requests that result in privilege elevation, with a maximum CVSS base score of 10.0 driven by a scope change (S:C). The CVSS vector (PR:N/UI:N) indicates no authentication or user interaction is required, and the CWE-918 classification confirms the root cause is unvalidated server-issued requests. No public exploit identified at time of analysis, and the flaw is not currently listed in CISA KEV.
Server-side request forgery in OpenViking before 0.3.4 allows authenticated low-privilege users to pivot the application server into an internal network proxy, reaching loopback addresses, RFC 1918 private ranges, link-local addresses, and cloud metadata endpoints such as AWS IMDS. By POSTing crafted URLs to /api/v1/resources, the attacker causes the server to issue outbound HEAD and GET requests with redirect-following enabled, then retrieves the responses through the normal content APIs - effectively mapping and interacting with internal services invisible from the public network. No public exploit identified at time of analysis; vendor-released patch in v0.3.4 is confirmed.
Server-side request forgery in Headroom LLM proxy (versions before 0.36.1) allows unauthenticated remote attackers to redirect proxy upstream requests to arbitrary internal, loopback, link-local, or RFC 1918 destinations - including cloud instance metadata endpoints such as 169.254.169.254 - by supplying a crafted x-headroom-base-url request header. The proxy returns upstream responses verbatim to the caller, disclosing internal service content; critically, it also forwards the original Authorization header to the attacker-designated host, enabling credential harvesting. Exploitation is trivially achievable against deployments using the vendor-shipped docker-compose.yml, which binds 0.0.0.0 and enforces no HEADROOM_PROXY_TOKEN by default - a configuration weakness the server itself warns about at startup. No public exploit or KEV listing is identified at time of analysis; a vendor patch is available in v0.36.1.
Cross-tenant root command execution in Apache CloudStack (4.14.0.0-4.20.3.0 and 4.21.0.0-4.22.1.0) allows an authenticated tenant holding only the default User role to run arbitrary shell commands as root on the KVM hypervisor host, which also runs other tenants' VMs. The flaw stems from CloudStack fetching a user-supplied .metalink file during directDownload template registration and dispatching its inner URLs to the KVM agent without re-validating them against the scheme allowlist; a related SSRF variant lets the Secondary Storage VM retrieve internal targets and persist them as downloadable templates. No public exploit identified at time of analysis, and no CVSS is provided by the vendor.
Server-Side Request Forgery in Apache CloudStack's webhook module lets attackers coerce the management server into issuing arbitrary HTTP requests via webhook delivery, reaching internal-only services and cloud metadata endpoints that are otherwise unreachable from outside. It affects Apache CloudStack 4.20.0.0 through 4.20.3.0 and 4.21.0.0 through 4.22.1.0, carries a CVSS 9.1 (high confidentiality and integrity impact), and has no public exploit identified at time of analysis. EPSS is low at 0.14% (4th percentile) and it is not on CISA KEV, indicating no observed active exploitation yet.
Server-Side Request Forgery in PTC Windchill PDMLink and PTC FlexPLM allows unauthenticated remote attackers to induce the server to issue arbitrary internal network requests by submitting maliciously crafted serialized data for deserialization. The underlying root cause is CWE-502 (Deserialization of Untrusted Data), where the deserialization process itself is the vector that triggers the SSRF condition, enabling lateral movement toward backend infrastructure. No public exploit code or CISA KEV listing has been identified at time of analysis, but the combination of network accessibility and no authentication requirement elevates practical risk for internet-exposed deployments.
SSRF in langchain-community's SitemapLoader defeats the documented `restrict_to_same_domain` security control by failing to apply it to nested sitemap index entries, allowing an attacker who influences an ingested sitemap to exfiltrate responses from internal network resources including loopback, link-local, and RFC-1918 addresses. Any LangChain-based pipeline consuming attacker-influenced sitemaps is affected; the CVSS 4.0 score of 7.7 reflects high confidentiality impact on downstream internal systems (SC:H) with no authentication or complexity requirements. No public exploit code has been confirmed and the flaw is not listed in CISA KEV at time of analysis, though the attack path is directly derivable from the vulnerability description.
Server-side request forgery in Microsoft Azure Virtual Machines enables a low-privileged authenticated attacker to forge internal network requests, ultimately achieving privilege escalation with full confidentiality, integrity, and availability impact across a changed scope. The CVSS vector (AV:N/AC:H/PR:L/S:C/C:H/I:H/A:H) confirms the vulnerability reaches beyond the Azure VM component itself, potentially compromising adjacent Azure services or internal metadata infrastructure. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, though Microsoft has released a patch via MSRC.
Server-side request forgery in Microsoft Azure Data Factory exposes sensitive internal information to unauthenticated remote attackers over a network. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms exploitation requires no authentication, no user interaction, and no special network positioning - any internet-reachable instance is in scope. No active exploitation has been confirmed by CISA KEV or public POC at time of analysis; SSVC rates exploitation as 'none' and EPSS at 0.99%, indicating limited real-world uptake despite the high CVSS base score.
Privilege elevation in Microsoft Entra ID (formerly Azure Active Directory) allows an authenticated, low-privileged attacker to abuse a server-side request forgery flaw (CWE-918) to reach protected internal endpoints and escalate privileges across a security scope over the network. The flaw carries a critical CVSS 9.9 with a scope change, meaning a foothold in one context can be leveraged to compromise resources beyond the attacker's original authorization. Microsoft has issued a service-side fix; there is no public exploit identified at time of analysis and no CISA KEV listing.
Elevation of privilege in Microsoft Exchange Online lets an unauthorized network attacker abuse a server-side request forgery (CWE-918) flaw to make the service issue attacker-controlled internal requests, crossing a privilege/trust boundary (CVSS scope change) to reach backend resources. The CVSS 10.0 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H) reflects unauthenticated, low-complexity network exploitation with high confidentiality, integrity, and availability impact. There is no public exploit identified at time of analysis and it is not on CISA KEV; Microsoft, the reporter, has already remediated the cloud service per its MSRC advisory.
Server-side request forgery in @platejs/docx-io prior to 53.3.2 allows network-accessible attackers to exfiltrate internal network content by supplying crafted HTML to the htmlToDocxBlob function. When attacker-controlled HTML containing img tags referencing internal URLs is processed server-side, the converter fetches those resources and embeds the response bytes into the generated DOCX, creating a response-disclosure channel to internal network infrastructure. No public exploit code has been identified at time of analysis, but the attack technique is well-understood and requires no specialized tooling beyond crafted HTML.
DNS rebinding in link-preview-js prior to 4.0.4 allows unauthenticated remote attackers to bypass the library's built-in SSRF protections and reach internal HTTP resources from the server hosting the preview service. The resolveDNSHost callback resolves a hostname once for validation but passes the original hostname back to the fetch layer, creating a time-of-check/time-of-use window that an attacker-controlled DNS server can exploit by returning a legitimate public IP during validation and an internal or loopback address on subsequent resolution. Vendor-released patch 4.0.4 is available; no public exploit identified at time of analysis, though the full fix is publicly documented in GitHub PR #181 and the GHSA-cpjf-6666-r8fx advisory.
Unauthenticated access to the Kafka Connect REST API in Splunk Connect for Kafka versions below 2.2.7 enables an SSRF-class attack that reconfigures the HTTP Event Collector destination to an attacker-controlled endpoint, resulting in theft of HEC authentication credentials and partial manipulation of event delivery to Splunk Enterprise. The connector's HEC endpoint validation does not enforce secure transport by default, meaning a non-TLS HTTP destination can be substituted without any authentication. No public exploit has been identified at time of analysis, but the attack requires no privileges and trivially low complexity, making any deployment with a network-exposed Kafka Connect REST API immediately actionable.
Server-Side Request Forgery (SSRF) in Cisco Talos Intelligence for Enterprise Security Cloud (versions below 1.0.3) allows an authenticated Splunk user holding the get_talos_enrichment capability to redirect the instance's outbound authenticated management requests to an attacker-controlled server, exposing Splunk management tokens. Successful exploitation grants the attacker full control over the Splunk instance, compromising the confidentiality, integrity, and availability of all data and configurations within it. No public exploit code or CISA KEV listing has been identified at time of analysis, but the patch is available and the CVSS score of 8.8 reflects the severity of token theft as a post-exploitation path.
Splunk Secure Gateway's failure to validate decoded report notification identifiers enables any authenticated low-privileged user to hijack system-level REST API sessions in Splunk Enterprise, achieving full configuration control and credential theft without requiring admin or power role. Affected versions span multiple Splunk Enterprise branches (9.4.x, 10.0.x, 10.2.x, 10.4.x) and Splunk Secure Gateway branches (3.8.x, 3.9.x, 3.10.x). No public exploit code or CISA KEV listing has been identified at time of analysis, but the low-complexity, low-privilege attack path and high-impact outcome (C:H/I:H/A:H) make this a realistic internal threat in any multi-tenant or shared Splunk deployment.
Server-Side Request Forgery in Termix prior to 2.3.2 allows authenticated users to weaponize the proxy connectivity test endpoint as an internal network scanner and cloud credential harvester. The POST /host/db/proxy/test endpoint blindly forwards raw TCP and SOCKS connections to attacker-controlled addresses supplied via singleProxy, proxyChain, and testTarget fields, enabling traversal to localhost services, RFC-1918 private networks, and link-local cloud metadata endpoints such as 169.254.169.254. Structured connection error responses and timing data leak host reachability, and successful metadata service access directly exposes cloud provider IAM credentials usable for lateral movement. No public exploit is identified at time of analysis, but the attack is trivially reproducible given the granular advisory disclosure.
Wekan's outgoing webhook URL validator in versions 8.36 through 9.73 allows authenticated board members to bypass SSRF protections by supplying DNS-resolvable hostnames - such as 169-254-169-254.nip.io resolving to the cloud metadata address 169.254.169.254 - that pass the synchronous string-based blocklist check but reach blocked internal IP ranges at request delivery time. Although the pre-existing delivery-time fetchSafe guard independently blocked the reported proof-of-concept IPv4 cloud metadata target since v8.35/v8.36, the inconsistent dual-validation architecture left IPv6 address family resolution unchecked and maintained a separate, drift-prone blocklist in ssrfGuard.js that could diverge from the input-time validator across software revisions. No public exploit identified at time of analysis; vendor-released patch is confirmed as version 9.74.
Server-Side Request Forgery in @contentful/mcp-tools allows any party who can invoke MCP tools or inject instructions into Contentful content to redirect the server's Contentful Management API Personal Access Token (PAT) to an attacker-controlled endpoint. The export_space and import_space tools spread LLM-controlled arguments - including host, proxy, rawProxy, and insecure - directly into the options object alongside the server-side PAT, causing the Contentful Management SDK to build its baseURL from attacker input and attach Authorization: Bearer <PAT> to all outgoing requests. A confirmed working proof-of-concept exists demonstrating both host-redirect and proxy-redirect vectors; no CISA KEV listing was identified at time of analysis, but the prompt injection path requires zero MCP privileges and represents a high-severity real-world risk for any AI agent reading untrusted Contentful content.
Authentication and authorization bypass in the cluster-proxy-addon component of Red Hat's Multicluster Engine for Kubernetes (MCE) lets an unauthenticated attacker who can reach the user-facing proxy route manipulate URL path segments to proxy requests to arbitrary services on any managed cluster. Because the flaw is a server-side request forgery (CWE-918) with a changed CVSS scope, a request to the hub's exposed route pivots into internal services on downstream clusters that were never meant to be externally reachable, enabling information disclosure and potential further compromise. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV; the CVSS base score is 9.3 (critical).
Server-Side Request Forgery in the Grav API plugin (grav-plugin-api) for Grav CMS before 1.0.6 lets a caller holding the api.webhooks.write permission register webhook URLs that the server dereferences with no protocol allow-listing. Because WebhookController.php validates the URL only with FILTER_VALIDATE_URL and WebhookDispatcher.php builds cURL without CURLOPT_PROTOCOLS/CURLOPT_REDIR_PROTOCOLS, an attacker can force the server to fetch file://, gopher://, dict://, and private/link-local targets, exfiltrating local files and internal HTTP responses including cloud metadata credentials. There is no public exploit identified at time of analysis and it is not in CISA KEV, but the root cause and fix are confirmed in the vendor advisory and commit.
Server-Side Request Forgery in Dell OpenManage Enterprise versions prior to 4.7.0 allows unauthenticated remote attackers to forge outbound HTTP requests from the server, exposing internal network resources and sensitive information. The CVSS scope-change indicator (S:C) confirms that forged requests can reach internal systems beyond the vulnerable host itself - a meaningful escalation for an enterprise IT management platform with privileged access to server infrastructure. No public exploit code and no CISA KEV listing have been identified at time of analysis; Dell has released version 4.7.0 as the remediated build per advisory DSA-2026-359.
Server-side request forgery in ArcadeDB before 26.8.1 allows authenticated low-privilege users to weaponize the OpenCypher LOAD CSV feature to issue arbitrary HTTP/HTTPS requests from the database server host, reaching internal network services and cloud metadata endpoints such as AWS IMDSv1. The server fetches and returns the content of these restricted destinations, enabling exfiltration of internal service data or cloud IAM credentials. No public exploit code or CISA KEV listing has been identified at time of analysis, but the CVSS 4.0 score of 8.3 with SC:H reflects meaningful lateral impact against adjacent cloud and internal infrastructure.
Non-blind SSRF in AIL Framework's crawler submission interface allows low-privileged authenticated users to pivot through the AIL server and reach internal networks, cloud metadata services (including 169.254.169.254), loopback addresses, and RFC1918 ranges. All versions covered by CPE cpe:2.3:a:ail-project:ail-framework:*:*:*:*:*:*:*:* are affected because manual crawler tasks bypass the existing domain blacklist via a priority-routing logic flaw, and crawled responses - including HTML, screenshots, and HAR data - are returned directly to the attacker, making exfiltration of cloud IAM credentials or internal service data straightforward. No public exploit has been identified and the vulnerability is not listed in CISA KEV; a vendor-released patch is available via upstream GitHub commit d7b60ff.
Server-Side Request Forgery in Animation Addons for Elementor WordPress plugin (versions before 2.7.2) permits unauthenticated remote attackers to coerce the WordPress server into issuing arbitrary HTTP requests to internal network hosts and relay the responses back to the attacker. The vulnerability stems from unsanitized user-supplied input being used directly to construct the host component of a server-side HTTP request. No public exploit or CISA KEV listing has been identified, and EPSS places exploitation probability at 0.15% (4th percentile), though SSVC notes the attack is automatable.
Server-side request forgery in Netflix Lemur's authority update path allows an authenticated user holding an authority role to redirect the Lemur backend into fetching arbitrary internal URLs, including cloud instance metadata endpoints such as 169.254.169.254. This is an incomplete-fix bypass of CVE-2026-55166 (GHSA-v2wp-frmc-5q3v): the creation-time allowlist check in `_validate_acme_url` was never applied to the `PUT /api/1/authorities/` update path, leaving the stored `acme_url` writable without re-validation. The fix is shipped in v1.9.3 with no public exploit identified at time of analysis.
Server-side request forgery in Netflix Lemur prior to 1.9.3 allows authority-role users to redirect ACME certificate issuance workflows to attacker-controlled servers, enabling JWS-signed HTTP requests to reach internal services or cloud metadata endpoints. The flaw exists in two components acting together: the PUT /api/1/authorities/ endpoint accepted acme_url modifications without revalidating the host against an allowlist, and the ACME ClientV2 blindly followed server-supplied URLs for nonce, order, authorization, and finalize operations without confirming the hostname matched the configured directory. No public exploit identified at time of analysis; vendor-released patch available in version 1.9.3.
Credential exfiltration via SSRF in AWX's GitHub webhook status callback affects Red Hat Ansible Automation Platform 2: an attacker holding admin role on a webhook-enabled job template can forge a signed GitHub pull request webhook with an arbitrary statuses_url, causing AWX to POST authenticated status updates - including the configured Git Personal Access Token in the Authorization header - to an attacker-controlled or internal endpoint. The Changed scope (S:C) in the CVSS 7.7 vector reflects that the leaked PAT extends attacker reach beyond AWX to connected Git repositories and any internal services reachable via SSRF. No public exploit identified at time of analysis, and no CISA KEV listing exists.
Server-side request forgery in the Red Hat Ansible Automation Platform 2 Controller's HashiCorp Vault credential plugin lets an authenticated user with credential-creation rights force the controller pod to leak its own Kubernetes service account token. When a HashiCorp Vault Secret Lookup credential configured for kubernetes_role authentication is tested, the kubernetes_auth() routine in awx_plugins/credentials/hashivault.py transmits the pod token to an attacker-supplied URL. With that token the attacker gains Kubernetes API access to control-plane namespaces, enabling full pod CRUD and secret reads including database credentials and the Django SECRET_KEY. No public exploit identified at time of analysis, and the flaw is not on the CISA KEV list.
Server-side request forgery in CodeWhale before 0.8.64 lets remote attackers reach internal-only IP addresses through the agent's fetch_url tool by exploiting a time-of-check-time-of-use gap in its DNS-pinning defense. Because the pre-fetch validator treated a failed DNS lookup as a pass-through ('let the HTTP request proceed and fail naturally'), an attacker who controls DNS responses can make the safety check see a non-resolving or benign answer while the real request resolves to an internal address, bypassing the SSRF allow/deny policy. No public exploit identified at time of analysis; a vendor patch and fix commit exist, and the issue was reported by VulnCheck.
Server-side request forgery in RAGFlow before v0.26.3 allows authenticated users who can create or trigger agent workflows to direct the server to make HTTP requests to arbitrary internal destinations, including RFC 1918 addresses, loopback interfaces, link-local ranges, and cloud instance metadata endpoints. The vulnerable 'Invoke' component in agent/component/invoke.py bypasses the shared assert_url_is_safe validator consistently applied in other fetch paths (crawler, SearXNG, file-upload, RSS), and returns the fetched response body directly to the caller. No public exploit has been identified at time of analysis, though two patch commits are publicly visible on GitHub and the vulnerable code location is documented in the references.
Unauthenticated SSRF in OttoKit WordPress plugin (≤1.1.35) allows any remote attacker without credentials to coerce the host server into making arbitrary outbound HTTP requests to attacker-controlled targets, including internal network resources and cloud metadata endpoints. The CVSS S:C (Scope Changed) rating confirms the vulnerability crosses security boundaries beyond the WordPress instance itself, enabling internal network reconnaissance, credential harvesting from cloud metadata services (e.g., AWS IMDSv1), or interaction with internal APIs. No active exploitation has been confirmed in CISA KEV, and no public exploit code has been identified at time of analysis.
Unauthenticated Server-Side Request Forgery in PDF Smart Viewer for Elementor (WordPress plugin by Deknows, versions up to and including 1.0.4) allows any remote, unauthenticated attacker to coerce the WordPress server into issuing arbitrary HTTP requests to attacker-controlled destinations. With a CVSS scope change (S:C), this vulnerability can be leveraged to probe and interact with internal network services not directly exposed to the internet, including cloud metadata endpoints, internal APIs, and adjacent infrastructure. No public exploit code or CISA KEV listing has been identified at time of analysis, but the zero-barrier entry (PR:N, UI:N, AC:L) makes it trivially scriptable.
Server-side request forgery in ArcadeDB before 26.8.1 enables authenticated attackers to bypass the IMPORT DATABASE command's hostname validator by exploiting a time-of-check/time-of-use gap: the validator resolves a hostname once, but the subsequent HTTP connection re-resolves it independently and follows redirects. This allows DNS rebinding or redirect-based bypass to reach cloud metadata endpoints such as the AWS IMDSv1 service, internal network services, or arbitrary local files on the host. No public exploit is identified at time of analysis, but the techniques involved are well-documented and the cloud credential exposure impact is severe on default cloud deployments.
Server-side request forgery in MLflow before 3.15.0 lets remote unauthenticated attackers coerce the server into making outbound requests to internal or cloud metadata endpoints via the POST /api/2.0/mlflow/webhooks/{id}/test endpoint. Because URL validation and the actual delivery re-resolve the hostname independently and follow redirects, an attacker can bypass the public-IP check and receive the target's response_status and response_body, enabling exfiltration of cloud credentials (e.g. from 169.254.169.254). No public exploit identified at time of analysis; the CVSS 9.3 rating and scope-change flag reflect the credential-theft potential of reaching metadata services.
Server-side request forgery in DataHub v1.5.0.1 lets a remote attacker coerce the server into fetching an attacker-supplied URL through its image-retrieval feature, with the response body and errors suppressed (blind SSRF). The reporter escalates this to arbitrary code execution, and the SSVC framework marks a proof-of-concept as available and the attack as automatable, though the flaw is not listed in CISA KEV and the EPSS probability is low at 0.24%.
Server-Side Request Forgery in Royal Elementor Addons for WordPress (versions ≤1.7.1064) allows authenticated Contributor-level users to persistently configure a malicious webhook URL via the Form Builder widget, which is then dispatched by an AJAX handler registered for both authenticated and unauthenticated callers - meaning the trigger phase requires no authentication at all. The root flaw is that wp_remote_post() is invoked on the stored URL with no host allowlist, no scheme restriction, and no private/loopback IP filtering, despite the plugin containing wpr_is_blocked_remote_host and wpr_is_private_or_local_ip helpers that are simply not called on this code path. No public exploit or CISA KEV listing has been identified at time of analysis.
Server-Side Request Forgery in Red Hat Quay's build API allows an authenticated user with repository write access to pivot into internal network segments via the Quay builder service. Exploitation requires FEATURE_BUILD_SUPPORT to be enabled and the attacker to hold at least write-level repository permissions. The CVSS vector (PR:L, C:H) reflects a meaningful but bounded threat: internal network reconnaissance and sensitive data disclosure are achievable, though no public exploit exists and EPSS sits at 0.13% (3rd percentile), indicating no observed widespread exploitation at time of analysis.
Server-side request forgery in Budibase automation steps (all versions prior to 3.41.3) exposes internal network resources - including cloud metadata endpoints, private databases, and Kubernetes APIs - to any authenticated user with automation creation rights. Five automation step types (outgoing webhook, Zapier, n8n, Slack, Discord) invoke node-fetch directly without any IP validation, completely bypassing the blacklist module that guards only the REST API integration. A second compounding flaw causes the REST API blacklist to default to an empty allowlist when the BLACKLIST_IPS environment variable is unset, meaning default Budibase deployments carry zero SSRF protection across all outbound request vectors. No CISA KEV listing exists, but the GHSA advisory provides source-level code references that substantially document the attack surface.
XXE injection in Datavane TIS v5.0.0 exposes authenticated attackers a path to SSRF and out-of-band file exfiltration against the server hosting the application. The `doEditWorkflow` endpoint accepts a `taskScript` parameter parsed by an unhardened Java `DocumentBuilderFactory` that resolves external entities and loads external DTDs, allowing a crafted XML payload to trigger outbound HTTP requests to attacker-controlled infrastructure and read local files accessible to the TIS process user, including configuration files and Derby database credentials. No public exploit has been identified at time of analysis, but VulnCheck has published a dedicated advisory and the upstream patch commit is publicly accessible, providing clear technical signal about the vulnerable code path.
DNS rebinding SSRF in Budibase before 3.40.0 exposes internal HTTP services to authenticated builder-level users who can bypass the platform's outbound fetch blacklist protections. Two distinct code paths are exploitable: the OpenAPI query import feature performs a raw fetch independently of its DNS validation guard, and the REST datasource/query execution path uses an undici dispatcher that re-resolves hostnames at connection time, defeating the pinned Node agent passed to fetchWithBlacklist(). No active exploitation is confirmed by CISA KEV, but the GHSA advisory includes detailed proof-of-concept reproduction steps with observed loopback canary responses, making this reliably reproducible by any builder-level account holder.
Server-side request forgery in Next AI Draw.io through 0.4.16 enables unauthenticated remote attackers to reach arbitrary internal HTTP services by exploiting a hostname validation bypass in the POST /api/parse-url endpoint. The validator inspects hostnames as string patterns only - without DNS resolution - allowing attackers to supply hostnames that pass the string check yet resolve to internal addresses, including cloud metadata endpoints such as the AWS IMDSv1 service. A publicly available proof-of-concept exists per VulnCheck; no CISA KEV listing has been identified at time of analysis.
Server-side request forgery in Gitea Open Source Git Server (all versions through 1.26.4) lets attackers abuse the repository migration and mirror features to reach internal network resources. Two distinct weaknesses are involved: a DNS-rebinding bypass where a hostname resolves to a permitted address during validation and to an internal address when the actual request is made, and a missing re-validation flaw where redirect or subsequent fetch targets are not re-checked against the allow/deny policy. No public exploit was identified at time of analysis, EPSS is low (0.15%), and it is not in CISA KEV, but the vendor rates technical impact as total and the issue is fixed in 1.27.0.
Unauthenticated SSRF in the Gutenverse Companion WordPress plugin (all versions through 2.5.1) allows remote unauthenticated attackers to induce the server to issue arbitrary HTTP requests to internal or external targets. The vulnerability carries a changed scope (S:C) in its CVSS vector, indicating potential for pivoting from the WordPress application layer to backend infrastructure. No public exploit code or CISA KEV listing has been identified at time of analysis, but the zero-authentication barrier makes this broadly exploitable against any unpatched WordPress installation running this plugin.
Server-side request forgery in Serendipity before 2.6.0 allows authenticated users with the adminImagesAdd permission to probe internal network services by submitting image URLs encoded as hex IPv4 addresses, IPv6 literals, or link-local ranges that bypass the serendipity_url_allowed() filter. The server fetches the internal resource and stores the response body in the publicly accessible uploads directory, enabling exfiltration of sensitive internal data such as cloud metadata or internal API responses. No public exploit or active exploitation (CISA KEV) has been identified at time of analysis, though the low attack complexity and well-understood SSRF technique lower the barrier for any attacker who obtains valid credentials.
Remote code execution and SSRF in FlowiseAI Flowise before 3.1.3 stems from a bypassable regex-based Python code validator in the CSV and Airtable Agent nodes, letting attackers smuggle malicious pandas calls through the unauthenticated prediction API via prompt injection. Because the validator blocklists rather than sandboxes, unblocked functions such as pd.read_json() can be abused to exfiltrate local datasets, reach internal services (SSRF), or execute arbitrary code. No public exploit identified at time of analysis, and it is not listed in CISA KEV; the reporting vendor VulnCheck and a GitHub Security Advisory (GHSA-w7x8-q2gp-5cgg) document the issue.
Server-Side Request Forgery in the Meeting Room Booking System (MRBS) import functionality allows remote attackers to force the application to fetch arbitrary private or local URIs, enabling potential pivot into internal networks or unauthorized integrity modification of internal services. The flaw affects all MRBS deployments prior to version 1.12.2, where the import feature accepts user-supplied URIs without restricting private address ranges or local endpoints. No public exploit code has been identified at time of analysis, but the unauthenticated network attack vector and low complexity make this trivially exploitable against internet-exposed instances.
Server-side request forgery and local file read in the OpenSearch Security Analytics plugin exposes authenticated users with low privileges as a vector for internal network reconnaissance and credential theft. The flaw resides in the threat intelligence feed parser, which fails to validate URL parameters submitted to the threat intel source configuration endpoint, allowing a crafted request to redirect server-side HTTP fetches to internal resources - including cloud metadata endpoints. Patch is confirmed available per Amazon's security bulletin AWS-2026-079; no public exploit code has been identified at time of analysis.
URLSecurityValidator SSRF bypass in compliance-trestle <= 4.0.3 allows a network-positioned attacker to reach cloud metadata services, loopback admin interfaces, and RFC 1918 internal networks by embedding IPv4-mapped IPv6 literals (e.g., [::ffff:169.254.169.254]) or the unspecified address 0.0.0.0 in OSCAL artifact import references processed by HTTPSFetcher or SFTPFetcher. Python's ipaddress module silently returns False - rather than raising TypeError - when comparing IPv6Address objects against IPv4Network ranges, so the validator's membership checks pass these forms through to requests.get unchanged. A publicly available proof-of-concept reproduces end-to-end IMDS credential exfiltration; no active exploitation is listed in CISA KEV and EPSS stands at 0.42%.
Server-side request forgery in Prowler's Lighthouse AI provider configuration allows an authenticated high-privilege user to redirect outbound HTTP requests - including the configured API key in the Authorization header - to attacker-controlled or internal network endpoints. Affected are all Prowler deployments prior to version 5.33.1 where the Lighthouse feature and an openai_compatible provider type are in use. No public exploit has been identified at time of analysis, but the attack path is straightforward for any user holding Lighthouse configuration permissions, making API key theft and internal network probing realistic objectives.
Server-Side Request Forgery in the PowerPress Podcasting plugin by Blubrry for WordPress (versions before 11.17.1) allows any authenticated Contributor-level user to supply arbitrary URLs in the Podcast Episode URL settings field, causing the server to issue unvalidated HTTP requests that can reach internal network services, cloud metadata endpoints, or other systems not directly exposed to the internet. The CVSS 7.1 score reflects high confidentiality impact against reachable internal services, and a publicly available proof-of-concept combined with a 13% EPSS score makes this an actionable priority for WordPress site operators running the plugin. No active exploitation has been confirmed in CISA KEV at time of analysis.
Server-side request forgery in Kestra's Pebble http() template function allows unauthenticated remote attackers to force the Kestra server to make outbound HTTP requests to private, loopback, or link-local addresses - including cloud Instance Metadata Service endpoints - by supplying a crafted URI inside an imported workflow flow. All Kestra releases prior to 2.0.0 are affected, with no scope restriction on reachable internal hosts, making cloud-hosted deployments particularly exposed to IAM credential theft via AWS/GCP/Azure IMDS APIs. No public exploit code or CISA KEV listing has been identified at time of analysis, but the combination of network-accessible, zero-authentication, low-complexity exploitation warrants high-priority remediation.
Privilege escalation via SSRF in Microsoft Office SharePoint exposes authenticated users to full system compromise - confidentiality, integrity, and availability all rated High. The CVSS vector (PR:L/AV:N/AC:L/UI:N) confirms that any authenticated SharePoint user can trigger the vulnerability over the network without additional complexity. No active exploitation or public exploit code has been identified at time of analysis, though the low attack complexity and broad privilege impact make this a credible near-term risk.
Server-side request forgery in Microsoft Office SharePoint enables low-privileged authenticated attackers to escalate privileges with no user interaction required, achieving high confidentiality, integrity, and availability impact. The flaw (CWE-918) allows a legitimate but low-privilege account holder to forge server-side HTTP requests, likely reaching internal administrative interfaces or credential endpoints inaccessible from the network perimeter. No public exploit code and no CISA KEV listing have been identified at time of analysis.
Server-Side Request Forgery in Apache Allura before 1.19.1 lets attackers abuse the project webhook feature to coerce the server into issuing arbitrary outbound HTTP requests, exposing internal services and cloud metadata endpoints. The flaw carries a CVSS 9.1 and is fixed in 1.19.1; it was disclosed via the Apache security team and oss-security on 2026-08-11. There is no public exploit identified at time of analysis and EPSS is low (0.20%, 11th percentile), indicating no observed weaponization yet.
SSRF in Microsoft Exchange Server enables authenticated, low-privilege network attackers to escalate privileges, with Microsoft reporting high confidentiality, integrity, and availability impact across Exchange 2016, 2019, and Subscription Edition. Vendor-released patches are available covering all affected cumulative update branches. No public exploit code exists and no active exploitation has been confirmed - EPSS sits at 0.62% (46th percentile) and CISA SSVC assigns Exploitation: none - meaning the CVSS 8.8 score outpaces current real-world threat activity.
Server-Side Request Forgery in Microsoft PowerShell Core versions 7.4.x, 7.5.x, and 7.6.x enables network-accessible unauthenticated attackers to forge outbound requests from the PowerShell process, resulting in high-impact information disclosure against resources outside the component's security boundary. The CVSS scope change (S:C) indicates that attacker-controlled SSRF requests can reach internal services inaccessible from the network perimeter, potentially exposing sensitive internal endpoints or metadata. No public exploit code has been identified at time of analysis, and active exploitation has not been confirmed by CISA KEV; Microsoft has released patched versions across all three affected branches.
Server-side request forgery with response read-back in SeaweedFS distributed storage (versions prior to 4.24) lets anyone able to reach a volume server's gRPC port coerce the server, via the unauthenticated VolumeServer.FetchAndWriteNeedle RPC, into fetching arbitrary attacker-chosen URLs and returning the response. Because the volume server gRPC plane is unauthenticated by default and the documented JWT hardening does not cover this RPC, an unauthenticated remote attacker (CVSS:3.1 AV:N/PR:N, base 9.3) can reach loopback, RFC 1918, link-local, and cloud metadata endpoints such as 169.254.169.254 to steal IAM credentials and pivot to internal services. No public exploit identified at time of analysis, and it is not in CISA KEV; the fix landed in version 4.24.
Type confusion in the Send Email node of the n8n workflow automation platform allows an attacker-supplied non-string expression value to pass uncoerced into Nodemailer, which then interprets it as a file path or URL rather than literal email content - enabling arbitrary local file disclosure and server-side request forgery (SSRF). Affected are n8n versions before 1.123.67, 2.x before 2.31.5, and 2.32.x before 2.32.1, as confirmed by GitHub Security Advisory GHSA-2x35-3fw4-9jr4. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog; exploitation depends on a specific non-default workflow configuration that requires an unauthenticated webhook, pre-configured SMTP credentials, and direct mapping of untrusted input into the email body field.
Server-Side Request Forgery in Red Hat OpenShift Container Platform 4's Dev Console webhook helpers allows authenticated users to coerce the console pod into issuing arbitrary outbound HTTP requests on their behalf. Because the console pod operates from a privileged network position within the cluster, this enables lateral movement to internal services - including the Kubernetes API server, metadata endpoints, and internal microservices - that would otherwise be unreachable from outside the cluster. No public exploit or CISA KEV listing has been identified at time of analysis, but the Scope:Changed CVSS metric reflects the cross-boundary nature of the impact.
Server-Side Request Forgery in the OpenShift Console Helm catalog proxy allows low-privileged namespace tenants to plant a malicious ProjectHelmChartRepository resource pointing to an attacker-controlled URL, causing the console pod to issue server-side fetches that bypass tenant egress restrictions. Combined with Helm catalog metadata poisoning and subsequent admin-mediated chart installation, this multi-stage attack chain enables privilege escalation within the cluster. No CISA KEV listing or public exploit code has been identified at time of analysis, though the CVSS Scope:Changed rating correctly reflects that the console pod's cross-boundary requests extend impact beyond the originating namespace.
Server-side request forgery in Pinry through 2.1.13 enables unauthenticated remote attackers to coerce the application server into issuing arbitrary HTTP requests to internal or external hosts via the pin-from-URL feature, which passes attacker-supplied URLs directly to Python's requests.get() without host allowlisting or IP validation. Because ALLOW_NEW_REGISTRATIONS defaults to true, no account or authentication is required to trigger the vulnerable endpoint, making every default-configured internet-exposed Pinry instance exploitable without any attacker preconditions. Attackers can leverage this to reach cloud metadata endpoints such as AWS IMDSv1 at 169.254.169.254, harvest IAM credentials, or probe internal services unreachable from the public internet; no public exploit has been identified at time of analysis and no CISA KEV listing is present.
Server-side request forgery in Dub's metatags edge endpoint allows unauthenticated remote attackers to direct the server to issue HTTP requests to arbitrary internal or external hosts. All Dub versions through 2026-07-10 are affected, with the root cause being the endpoint's acceptance of caller-supplied URLs without any denylist filtering or authentication requirement. Attackers can leverage this to probe RFC 1918 address space, enumerate internal services, or exfiltrate credentials from cloud metadata endpoints such as AWS IMDSv1; no public exploit code or active exploitation (CISA KEV) has been identified at time of analysis.
Unauthenticated server-side request forgery in Commvault Command Center's legacy endpoint allows a remote, unauthenticated attacker to cause the server to issue HTTP requests to arbitrary URLs, exposing internal services, cloud metadata endpoints, and credentials accessible from the Command Center's privileged network position. All versions of Commvault Cloud are indicated as affected per wildcard CPE, with Commvault releasing a resolved maintenance release per advisory CV_2026_07_5. No public exploit has been identified at time of analysis, and no CISA KEV listing is present, but the CVSS 4.0 score of 8.8 with no authentication or precondition requirements makes this a high-priority remediation target in enterprise environments.
Server-Side Request Forgery in MISP's cti-transmute tool allows unauthenticated network attackers to leverage the /fetch_misp_event and /misp_search_events endpoints as a proxy into the server's internal network by supplying a domain name whose DNS record resolves to a private or reserved IP address. The validation logic checked IP literals against blocked ranges but unconditionally trusted domain names, creating a trivially exploitable DNS-bypass gap confirmed by the upstream commit to expose full internal response bodies to anonymous callers. No public exploit has been identified and the vulnerability is not in the CISA KEV catalog, but the zero-prerequisite attack surface against potentially sensitive threat intelligence infrastructure makes prompt remediation essential.
Server-side request forgery in Grafana's mcp-grafana (Grafana MCP Server) lets an authenticated caller override the outbound request destination via the X-Grafana-URL header while using the grafana_api_request tool to control HTTP method, path, and body. Because the destination is never constrained to the configured Grafana instance, callers can pivot the server into internal, loopback, and link-local services-including cloud metadata endpoints-and read the responses. This is an incomplete-fix follow-on to CVE-2026-15583, which stopped the service-account token from leaking to unintended hosts but left the destinations themselves unrestricted; no public exploit identified at time of analysis.
Server-Side Request Forgery in usememos/memos through v0.30.0 allows authenticated users to redirect server-side HTTP requests to arbitrary internal network addresses by configuring a malicious webhook target URL. The CVSS S:C (Scope Changed) rating reflects that exploitation breaks the application boundary, enabling access to internal infrastructure such as cloud metadata endpoints, internal APIs, or RFC1918-addressed services. A publicly available proof-of-concept exists via GitHub gist; however, EPSS remains low at 0.22% (13th percentile), indicating limited observed exploitation in the wild at time of analysis despite the high CVSS score of 8.5.
Arbitrary file read and SSRF in Firecrawl before 2.11.32 lets an API caller exfiltrate files from the extraction worker and reach internal/external HTTP endpoints by abusing JSON-schema dereferencing. The extract feature passes user-supplied schemas to the json-schema-ref-parser library with default resolvers, so a $ref placed inside default, const, or enum fields (which AJV does not traverse) is resolved against the local filesystem or network; a deliberately triggered dereference error then leaks the resolved file contents back through the extraction API's persisted error message. No public exploit or CISA KEV listing is identified at time of analysis, but the fix commit ships security regression tests demonstrating the file:// and metadata-endpoint attack paths.
Server-side request forgery in gabehf/Koito through v0.3.2 lets authenticated users coerce the application server into issuing arbitrary HTTP requests to internal or external hosts via the album image endpoint. The CVSS scope-change rating (S:C) reflects that exploitation reaches beyond the vulnerable component itself - an attacker can pivot through the server to probe cloud metadata services, internal APIs, or RFC-1918 hosts unreachable directly from the internet. No public exploit or active exploitation is identified at time of analysis, but the low attack complexity and lack of URL validation make this straightforward to abuse once authenticated.
Unauthenticated SSRF in duhow/xiaoai-patch (all versions through commit fb07049) allows any remote attacker to force the Xiaomi XiaoAI smart speaker's API server to issue HTTP requests to arbitrary internal or external URLs. The /auth endpoint in api/main.py blindly accepts a user-supplied url POST parameter to redirect toward a Home Assistant instance without destination validation, enabling internal network scanning and access to internal services from the speaker's network vantage point. No public exploit code has been identified at time of analysis, and this CVE is not listed in the CISA KEV catalog.
Server-side request forgery in Automatisch through commit 41f3c56 exposes internal network services to any authenticated user holding the 'manage Flow' permission. The HTTP Request app's Custom Request action passes caller-supplied URLs directly to the backend HTTP client with no allowlist, blocklist, or redirect controls, enabling full response-body retrieval from cloud metadata endpoints, internal APIs, and private network hosts. No public exploit or CISA KEV listing has been identified at time of analysis, but the scope-changed, high-confidentiality CVSS vector reflects the severity of lateral access achievable through this single permission.
Server-Side Request Forgery in the Telefunken TE24553B45V2DZ Smart TV firmware V2.78.0.0 allows a network-adjacent unauthenticated attacker to abuse the SmartCenter browserseturl command, redirecting the device's embedded browser to loopback (127.0.0.1) and internal network destinations that are otherwise unreachable through normal browser navigation. The Vestel MB181 / Voltron181 / TiVo OS platform's SmartCenter component fails to restrict target URL schemes and destinations, enabling the TV to serve as an internal SSRF proxy against its own locally-running services. No public exploit code has been identified and this CVE is absent from the CISA KEV catalog; however, the zero-privilege, adjacent-network attack posture makes exploitation accessible to any local network attacker, including guests in hospitality deployments.
Server-side request forgery in Microsoft Office SharePoint lets a remote, unauthenticated attacker coerce the server into issuing attacker-controlled requests, enabling spoofing across a network per Microsoft's classification. The CVSS 3.1 base score is 9.6 (critical) with a changed scope, and exploitation requires a victim to interact with attacker-supplied content (UI:R). There is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Server-side request forgery in Fedify's getNodeInfo() function allows unauthenticated remote attackers to pivot through a Fedify server into internal network services - including loopback interfaces, cloud metadata endpoints (e.g., AWS IMDS at 169.254.169.254), and RFC 1918 private networks - by returning a crafted /.well-known/nodeinfo document with a malicious links[].href value. Affected versions span the 1.9 through 2.3 maintenance lines starting from 1.2.0, with response bodies from internal services returned directly to the initiating attacker. No confirmed active exploitation (not in CISA KEV) and no POC status was provided in the input data, but SSRF against cloud metadata is a high-value, well-understood attack path.
Server-side request forgery in Dradis Community Edition 5.1.0-5.2.0 allows any authenticated non-admin user to hijack the AI provider configuration and redirect server-initiated HTTP requests to arbitrary URLs, including internal cloud metadata endpoints such as 169.254.169.254. A broken authorization gate in ProvidersController and AgentsController is conditioned on the Ruby constant Dradis::Pro, which is never defined in CE builds, so the admin_required filter is silently skipped for all CE installations. Non-2xx responses from attacker-supplied URLs are reflected verbatim to the attacker's browser via ActionCable/Turbo Stream, enabling exfiltration of internal service content. No public exploit code or CISA KEV listing has been identified at time of analysis.
Server-side request forgery in Adobe Campaign Classic (ACC) escalates to arbitrary code execution in the context of the running user, giving an unauthenticated network attacker full control per Adobe's CVSS:3.1 base score of 10.0 (scope-changed). The flaw lets an attacker coerce the server into making attacker-controlled requests that pivot into code execution with no user interaction. No public exploit has been identified at time of analysis and the issue is not listed in CISA KEV; the only reference is an Adobe advisory (APSB26-134) served from an internal, non-public host and could not be independently verified.
Server-Side Request Forgery (SSRF) in JFrog Artifactory allows a low-privileged authenticated user with read access to a remote VCS repository to replace the repository's configured origin URL or supply an arbitrary absolute VCS data URL, causing Artifactory's server process to issue outbound HTTP requests to attacker-controlled destinations - including internal network services, cloud metadata endpoints, or other infrastructure inaccessible from the public internet. The scope-changed CVSS vector (S:C) confirms the impact extends beyond Artifactory itself to systems on its internal network segment. No public exploit identified at time of analysis, and this vulnerability is not listed in the CISA KEV catalog.
Server-Side Request Forgery in PraisonAI's Jobs API (pip/praisonai < 4.6.58) results from two compounding flaws: a fail-open DNS error handler in `JobSubmitRequest.validate_webhook_url()` that silently accepts any webhook URL when `socket.gaierror` is raised, and a TOCTOU race where `JobExecutor._send_webhook()` performs a completely independent DNS resolution via `httpx.AsyncClient` minutes to hours after validation. Authenticated attackers with a valid API bearer token can submit a job whose `webhook_url` hostname returns NXDOMAIN at validation time, then update DNS to a private IP before job completion, causing the executor to POST job result data to internal infrastructure. A detailed proof-of-concept is publicly available in GHSA-rg5q-pp8p-f7jm; no public exploit identified at time of analysis beyond the PoC, and this CVE is not listed in CISA KEV.
Server-Side Request Forgery in praisonaiagents (pip package, versions < 1.6.58) allows any attacker who can influence an AI agent's crawl target - via crafted task instructions or prompt injection embedded in previously crawled content - to exfiltrate cloud instance metadata (including IAM credentials), internal localhost services, and RFC1918 API endpoints. The web_crawl tool's SSRF protection validates only the initial URL's hostname IP, then invokes httpx with follow_redirects=True, allowing an attacker-controlled public URL to 302-redirect the agent to 169.254.169.254 or 127.0.0.1 without any re-validation. This is an incomplete fix for a prior SSRF class in the same component. A fully functional proof-of-concept is publicly documented in GHSA-5r34-2g38-6569, and no public exploit identified at time of analysis beyond the PoC; no CISA KEV listing is present.
Server-side request forgery in Ech0 before version 4.7.3 allows authenticated users to pivot through the application server to reach internal infrastructure, including cloud provider metadata APIs and Kubernetes service endpoints. The root cause is a missing URL-validation call: `fetchPeerConnectInfo` in `internal/service/connect/connect.go` invokes the unguarded `SendRequest` helper rather than the `SendSafeRequest` variant that enforces `ValidatePublicHTTPURL` private-IP blocking. A working proof-of-concept demonstrating AWS IMDSv1 and Kubernetes API enumeration is publicly available in the GHSA advisory; no active exploitation via CISA KEV has been confirmed, though the CVSS 4.0 score of 8.3 with SC:H reflects elevated impact potential for cloud-hosted deployments.
Server-side request forgery in Apache Hive versions 2.1.0 through 4.2.0 lets an authenticated user with CREATE TABLE rights coerce the HiveServer2/Metastore process into fetching an attacker-chosen URL by planting a crafted avro.schema.url table property on an Avro table that is later queried. The fetch runs with the Hive service identity, exposing cloud instance metadata (e.g. 169.254.169.254), internal-only network services, and local files. No public exploit is identified at time of analysis and EPSS is low (0.29%), but the CVSS 9.1 rating and low attack complexity make it a meaningful post-authentication risk; upgrade to 4.2.1 resolves it.
Server-side request forgery in NLTK before 3.10.3 allows unauthenticated remote attackers to reach internal HTTP services and load attacker-controlled downloader indexes when an HTTP proxy is configured. The flaw sits in nltk.pathsec.urlopen and its callers (nltk.data.load, nltk.downloader.Downloader.index, nltk.downloader.Downloader.download): local hostname validation passes the supplied public URL, but proxy-handler inheritance then replaces NLTK's safe URL handlers so the actual fetch is executed by the proxy against an internally-resolvable destination that is never re-validated. No public exploit code or CISA KEV listing has been identified at time of analysis; the CVSS 4.0 base score is 8.7, reflecting high confidentiality impact under network-accessible, unauthenticated conditions.
Server-side request forgery in Hi.Events (all versions prior to 1.11.1-beta) allows an authenticated platform user to exfiltrate responses from internal network services, including cloud metadata endpoints, by exploiting a time-of-check/time-of-use gap in webhook URL validation. The registration-time guard in NoInternalUrlRule is never repeated at dispatch, and Guzzle's default redirect-following allows a destination that answers with a redirect to a loopback or RFC-1918 address to cause the server to issue the secondary request. Critically, this is not blind SSRF: WebhookResponseHandlerService stores the response body and WebhookLogResource exposes it via the webhook logs API, enabling direct credential or secret exfiltration. No public exploit has been identified at time of analysis, and the CVE is not listed in CISA KEV.
SSRF vulnerabilities in AWX notification backends (webhook, Mattermost, Rocket.Chat, and Grafana) allow an authenticated organization notification administrator to cause the AWX control node to issue outbound HTTP requests to internal, loopback, or RFC-1918 addresses that are not externally reachable. Beyond basic SSRF, the webhook backend compounds the risk by following HTTP redirects and replaying configured Basic Authentication credentials to the redirect destination regardless of host change, enabling credential exfiltration to attacker-controlled endpoints; the Grafana backend similarly exposes its API key by forwarding the Authorization header verbatim to any configured target URL. No public exploit has been identified at time of analysis, but the Changed scope and high confidentiality impact in the CVSS vector reflect significant real-world risk given the network position AWX control nodes typically occupy.
PDF export in RansomLook allows authenticated analysts to read arbitrary server-side files and conduct server-side request forgery by embedding crafted resource references in analysis documents. Prior to the patch, WeasyPrint's default URL fetcher resolved any scheme - including file:// and http:// - using the privileges and network access of the RansomLook server process, enabling exfiltration of local configuration and credentials or enumeration of internal network services. No public exploit code or CISA KEV listing exists at time of analysis; a fix is confirmed via GitHub commit 34dc0285583dae483b4d48c8e98fff942b755f5f, which introduces a strict URL allowlist restricting rendering to data: URIs, the report logo, and analysis asset files.
Server-side request forgery in Hugo static site generator (versions 0.91.0 through 0.165.0) allows an attacker who can supply a URL through site content - via front-matter fields or a connected CMS - to silently fetch loopback, RFC 1918, or cloud-metadata endpoints during the build process, embedding the internal response directly into the published static output. The security.http.urls allowlist, Hugo's only guard on resources.GetRemote outbound fetches, evaluates hostname strings without performing DNS resolution, meaning any registered domain whose A record points to a private or metadata IP bypasses the policy entirely, and no dial-time hook in the HTTP client provides a second check. No public exploit code has been identified at time of analysis, but the attack requires only DNS control and content-write access, making it operationally straightforward in CI/CD-integrated deployments.
Server-side request forgery and address-policy bypass in fast-uri, the Node.js URI parser used widely in the fastify ecosystem, allows remote unauthenticated attackers to redirect outbound requests from a target application to local or private IPv6 addresses by submitting crafted bracketed IPv6 literals with invalid trailing characters. The custom IPv6 parser silently normalizes malformed literals - collapsing some to the unspecified address (loopback) and others to private-range addresses - and returns no error on the parsed result, defeating any application-level error checking. No public exploit code or CISA KEV listing has been identified at time of analysis, but the attack requires no special privileges and low complexity, making automated exploitation plausible against any exposed application that normalizes untrusted URLs through an affected fast-uri version.
Parsing and serialization inconsistency in fast-uri, the Node.js URI parser core to the Fastify ecosystem, allows network-accessible, unauthenticated attackers to supply percent-encoded slashes in the scheme component, causing the library to report host as undefined during parsing while serialization emits a network-path reference with an attacker-controlled authority. Applications that allowlist requests on the parsed host value, or that treat a no-authority parse result as safe to resolve against a base URI, are bypassed - enabling server-side request forgery, off-site redirects, and address-policy evasion. No public exploit has been identified at time of analysis, but the CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms exploitation requires no authentication and no special configuration, making affected deployments an immediate upgrade priority.
Double-decoding of percent-encoded hostnames in fast-uri (Node.js URI parser) creates a server-side request forgery and host-policy bypass primitive in versions 2.4.1-2.4.4, 3.1.2-3.1.5, and 4.0.0-4.1.2. The library decodes percent escapes once during hostname parsing and again during authority recomposition, so a single normalize or resolve call on a doubly-encoded input can silently resolve to a different network destination - including loopback addresses - than the encoded form represents. Any application layer sitting fast-uri in front of outbound routing guards, redirect allow-lists, or host-policy checks is therefore vulnerable to SSRF. This is an incomplete-fix variant of CVE-2026-6322; no public exploit code or active exploitation (CISA KEV) has been identified at time of analysis.
Server-Side Request Forgery in the Mailgun for WordPress plugin (versions up to and including 2.2.0) lets unauthenticated attackers coerce the WordPress server into making authenticated requests to arbitrary Mailgun API endpoints using the site's own stored API key. Because the add_list() function trusts user-controlled array keys from $_POST['addresses'] and only runs them through sanitize_text_field(), an attacker can path-traverse to any Mailgun endpoint - notably creating inbound email-forwarding routes to intercept password-reset messages and take over the administrator account. Reported by Wordfence with a CVSS of 9.8; no public exploit identified at time of analysis and no CISA KEV listing.
Server-side request forgery in Microsoft's Azure SQL Database cloud service lets an unauthorized network attacker coerce the service into making backend requests that result in privilege elevation, with a maximum CVSS base score of 10.0 driven by a scope change (S:C). The CVSS vector (PR:N/UI:N) indicates no authentication or user interaction is required, and the CWE-918 classification confirms the root cause is unvalidated server-issued requests. No public exploit identified at time of analysis, and the flaw is not currently listed in CISA KEV.
Server-side request forgery in OpenViking before 0.3.4 allows authenticated low-privilege users to pivot the application server into an internal network proxy, reaching loopback addresses, RFC 1918 private ranges, link-local addresses, and cloud metadata endpoints such as AWS IMDS. By POSTing crafted URLs to /api/v1/resources, the attacker causes the server to issue outbound HEAD and GET requests with redirect-following enabled, then retrieves the responses through the normal content APIs - effectively mapping and interacting with internal services invisible from the public network. No public exploit identified at time of analysis; vendor-released patch in v0.3.4 is confirmed.
Server-side request forgery in Headroom LLM proxy (versions before 0.36.1) allows unauthenticated remote attackers to redirect proxy upstream requests to arbitrary internal, loopback, link-local, or RFC 1918 destinations - including cloud instance metadata endpoints such as 169.254.169.254 - by supplying a crafted x-headroom-base-url request header. The proxy returns upstream responses verbatim to the caller, disclosing internal service content; critically, it also forwards the original Authorization header to the attacker-designated host, enabling credential harvesting. Exploitation is trivially achievable against deployments using the vendor-shipped docker-compose.yml, which binds 0.0.0.0 and enforces no HEADROOM_PROXY_TOKEN by default - a configuration weakness the server itself warns about at startup. No public exploit or KEV listing is identified at time of analysis; a vendor patch is available in v0.36.1.
Cross-tenant root command execution in Apache CloudStack (4.14.0.0-4.20.3.0 and 4.21.0.0-4.22.1.0) allows an authenticated tenant holding only the default User role to run arbitrary shell commands as root on the KVM hypervisor host, which also runs other tenants' VMs. The flaw stems from CloudStack fetching a user-supplied .metalink file during directDownload template registration and dispatching its inner URLs to the KVM agent without re-validating them against the scheme allowlist; a related SSRF variant lets the Secondary Storage VM retrieve internal targets and persist them as downloadable templates. No public exploit identified at time of analysis, and no CVSS is provided by the vendor.
Server-Side Request Forgery in Apache CloudStack's webhook module lets attackers coerce the management server into issuing arbitrary HTTP requests via webhook delivery, reaching internal-only services and cloud metadata endpoints that are otherwise unreachable from outside. It affects Apache CloudStack 4.20.0.0 through 4.20.3.0 and 4.21.0.0 through 4.22.1.0, carries a CVSS 9.1 (high confidentiality and integrity impact), and has no public exploit identified at time of analysis. EPSS is low at 0.14% (4th percentile) and it is not on CISA KEV, indicating no observed active exploitation yet.
Server-Side Request Forgery in PTC Windchill PDMLink and PTC FlexPLM allows unauthenticated remote attackers to induce the server to issue arbitrary internal network requests by submitting maliciously crafted serialized data for deserialization. The underlying root cause is CWE-502 (Deserialization of Untrusted Data), where the deserialization process itself is the vector that triggers the SSRF condition, enabling lateral movement toward backend infrastructure. No public exploit code or CISA KEV listing has been identified at time of analysis, but the combination of network accessibility and no authentication requirement elevates practical risk for internet-exposed deployments.
SSRF in langchain-community's SitemapLoader defeats the documented `restrict_to_same_domain` security control by failing to apply it to nested sitemap index entries, allowing an attacker who influences an ingested sitemap to exfiltrate responses from internal network resources including loopback, link-local, and RFC-1918 addresses. Any LangChain-based pipeline consuming attacker-influenced sitemaps is affected; the CVSS 4.0 score of 7.7 reflects high confidentiality impact on downstream internal systems (SC:H) with no authentication or complexity requirements. No public exploit code has been confirmed and the flaw is not listed in CISA KEV at time of analysis, though the attack path is directly derivable from the vulnerability description.
Server-side request forgery in Microsoft Azure Virtual Machines enables a low-privileged authenticated attacker to forge internal network requests, ultimately achieving privilege escalation with full confidentiality, integrity, and availability impact across a changed scope. The CVSS vector (AV:N/AC:H/PR:L/S:C/C:H/I:H/A:H) confirms the vulnerability reaches beyond the Azure VM component itself, potentially compromising adjacent Azure services or internal metadata infrastructure. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, though Microsoft has released a patch via MSRC.
Server-side request forgery in Microsoft Azure Data Factory exposes sensitive internal information to unauthenticated remote attackers over a network. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms exploitation requires no authentication, no user interaction, and no special network positioning - any internet-reachable instance is in scope. No active exploitation has been confirmed by CISA KEV or public POC at time of analysis; SSVC rates exploitation as 'none' and EPSS at 0.99%, indicating limited real-world uptake despite the high CVSS base score.
Privilege elevation in Microsoft Entra ID (formerly Azure Active Directory) allows an authenticated, low-privileged attacker to abuse a server-side request forgery flaw (CWE-918) to reach protected internal endpoints and escalate privileges across a security scope over the network. The flaw carries a critical CVSS 9.9 with a scope change, meaning a foothold in one context can be leveraged to compromise resources beyond the attacker's original authorization. Microsoft has issued a service-side fix; there is no public exploit identified at time of analysis and no CISA KEV listing.
Elevation of privilege in Microsoft Exchange Online lets an unauthorized network attacker abuse a server-side request forgery (CWE-918) flaw to make the service issue attacker-controlled internal requests, crossing a privilege/trust boundary (CVSS scope change) to reach backend resources. The CVSS 10.0 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H) reflects unauthenticated, low-complexity network exploitation with high confidentiality, integrity, and availability impact. There is no public exploit identified at time of analysis and it is not on CISA KEV; Microsoft, the reporter, has already remediated the cloud service per its MSRC advisory.
Server-side request forgery in @platejs/docx-io prior to 53.3.2 allows network-accessible attackers to exfiltrate internal network content by supplying crafted HTML to the htmlToDocxBlob function. When attacker-controlled HTML containing img tags referencing internal URLs is processed server-side, the converter fetches those resources and embeds the response bytes into the generated DOCX, creating a response-disclosure channel to internal network infrastructure. No public exploit code has been identified at time of analysis, but the attack technique is well-understood and requires no specialized tooling beyond crafted HTML.
DNS rebinding in link-preview-js prior to 4.0.4 allows unauthenticated remote attackers to bypass the library's built-in SSRF protections and reach internal HTTP resources from the server hosting the preview service. The resolveDNSHost callback resolves a hostname once for validation but passes the original hostname back to the fetch layer, creating a time-of-check/time-of-use window that an attacker-controlled DNS server can exploit by returning a legitimate public IP during validation and an internal or loopback address on subsequent resolution. Vendor-released patch 4.0.4 is available; no public exploit identified at time of analysis, though the full fix is publicly documented in GitHub PR #181 and the GHSA-cpjf-6666-r8fx advisory.
Unauthenticated access to the Kafka Connect REST API in Splunk Connect for Kafka versions below 2.2.7 enables an SSRF-class attack that reconfigures the HTTP Event Collector destination to an attacker-controlled endpoint, resulting in theft of HEC authentication credentials and partial manipulation of event delivery to Splunk Enterprise. The connector's HEC endpoint validation does not enforce secure transport by default, meaning a non-TLS HTTP destination can be substituted without any authentication. No public exploit has been identified at time of analysis, but the attack requires no privileges and trivially low complexity, making any deployment with a network-exposed Kafka Connect REST API immediately actionable.
Server-Side Request Forgery (SSRF) in Cisco Talos Intelligence for Enterprise Security Cloud (versions below 1.0.3) allows an authenticated Splunk user holding the get_talos_enrichment capability to redirect the instance's outbound authenticated management requests to an attacker-controlled server, exposing Splunk management tokens. Successful exploitation grants the attacker full control over the Splunk instance, compromising the confidentiality, integrity, and availability of all data and configurations within it. No public exploit code or CISA KEV listing has been identified at time of analysis, but the patch is available and the CVSS score of 8.8 reflects the severity of token theft as a post-exploitation path.
Splunk Secure Gateway's failure to validate decoded report notification identifiers enables any authenticated low-privileged user to hijack system-level REST API sessions in Splunk Enterprise, achieving full configuration control and credential theft without requiring admin or power role. Affected versions span multiple Splunk Enterprise branches (9.4.x, 10.0.x, 10.2.x, 10.4.x) and Splunk Secure Gateway branches (3.8.x, 3.9.x, 3.10.x). No public exploit code or CISA KEV listing has been identified at time of analysis, but the low-complexity, low-privilege attack path and high-impact outcome (C:H/I:H/A:H) make this a realistic internal threat in any multi-tenant or shared Splunk deployment.
Server-Side Request Forgery in Termix prior to 2.3.2 allows authenticated users to weaponize the proxy connectivity test endpoint as an internal network scanner and cloud credential harvester. The POST /host/db/proxy/test endpoint blindly forwards raw TCP and SOCKS connections to attacker-controlled addresses supplied via singleProxy, proxyChain, and testTarget fields, enabling traversal to localhost services, RFC-1918 private networks, and link-local cloud metadata endpoints such as 169.254.169.254. Structured connection error responses and timing data leak host reachability, and successful metadata service access directly exposes cloud provider IAM credentials usable for lateral movement. No public exploit is identified at time of analysis, but the attack is trivially reproducible given the granular advisory disclosure.
Wekan's outgoing webhook URL validator in versions 8.36 through 9.73 allows authenticated board members to bypass SSRF protections by supplying DNS-resolvable hostnames - such as 169-254-169-254.nip.io resolving to the cloud metadata address 169.254.169.254 - that pass the synchronous string-based blocklist check but reach blocked internal IP ranges at request delivery time. Although the pre-existing delivery-time fetchSafe guard independently blocked the reported proof-of-concept IPv4 cloud metadata target since v8.35/v8.36, the inconsistent dual-validation architecture left IPv6 address family resolution unchecked and maintained a separate, drift-prone blocklist in ssrfGuard.js that could diverge from the input-time validator across software revisions. No public exploit identified at time of analysis; vendor-released patch is confirmed as version 9.74.
Server-Side Request Forgery in @contentful/mcp-tools allows any party who can invoke MCP tools or inject instructions into Contentful content to redirect the server's Contentful Management API Personal Access Token (PAT) to an attacker-controlled endpoint. The export_space and import_space tools spread LLM-controlled arguments - including host, proxy, rawProxy, and insecure - directly into the options object alongside the server-side PAT, causing the Contentful Management SDK to build its baseURL from attacker input and attach Authorization: Bearer <PAT> to all outgoing requests. A confirmed working proof-of-concept exists demonstrating both host-redirect and proxy-redirect vectors; no CISA KEV listing was identified at time of analysis, but the prompt injection path requires zero MCP privileges and represents a high-severity real-world risk for any AI agent reading untrusted Contentful content.
Authentication and authorization bypass in the cluster-proxy-addon component of Red Hat's Multicluster Engine for Kubernetes (MCE) lets an unauthenticated attacker who can reach the user-facing proxy route manipulate URL path segments to proxy requests to arbitrary services on any managed cluster. Because the flaw is a server-side request forgery (CWE-918) with a changed CVSS scope, a request to the hub's exposed route pivots into internal services on downstream clusters that were never meant to be externally reachable, enabling information disclosure and potential further compromise. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV; the CVSS base score is 9.3 (critical).
Server-Side Request Forgery in the Grav API plugin (grav-plugin-api) for Grav CMS before 1.0.6 lets a caller holding the api.webhooks.write permission register webhook URLs that the server dereferences with no protocol allow-listing. Because WebhookController.php validates the URL only with FILTER_VALIDATE_URL and WebhookDispatcher.php builds cURL without CURLOPT_PROTOCOLS/CURLOPT_REDIR_PROTOCOLS, an attacker can force the server to fetch file://, gopher://, dict://, and private/link-local targets, exfiltrating local files and internal HTTP responses including cloud metadata credentials. There is no public exploit identified at time of analysis and it is not in CISA KEV, but the root cause and fix are confirmed in the vendor advisory and commit.
Server-Side Request Forgery in Dell OpenManage Enterprise versions prior to 4.7.0 allows unauthenticated remote attackers to forge outbound HTTP requests from the server, exposing internal network resources and sensitive information. The CVSS scope-change indicator (S:C) confirms that forged requests can reach internal systems beyond the vulnerable host itself - a meaningful escalation for an enterprise IT management platform with privileged access to server infrastructure. No public exploit code and no CISA KEV listing have been identified at time of analysis; Dell has released version 4.7.0 as the remediated build per advisory DSA-2026-359.
Server-side request forgery in ArcadeDB before 26.8.1 allows authenticated low-privilege users to weaponize the OpenCypher LOAD CSV feature to issue arbitrary HTTP/HTTPS requests from the database server host, reaching internal network services and cloud metadata endpoints such as AWS IMDSv1. The server fetches and returns the content of these restricted destinations, enabling exfiltration of internal service data or cloud IAM credentials. No public exploit code or CISA KEV listing has been identified at time of analysis, but the CVSS 4.0 score of 8.3 with SC:H reflects meaningful lateral impact against adjacent cloud and internal infrastructure.
Non-blind SSRF in AIL Framework's crawler submission interface allows low-privileged authenticated users to pivot through the AIL server and reach internal networks, cloud metadata services (including 169.254.169.254), loopback addresses, and RFC1918 ranges. All versions covered by CPE cpe:2.3:a:ail-project:ail-framework:*:*:*:*:*:*:*:* are affected because manual crawler tasks bypass the existing domain blacklist via a priority-routing logic flaw, and crawled responses - including HTML, screenshots, and HAR data - are returned directly to the attacker, making exfiltration of cloud IAM credentials or internal service data straightforward. No public exploit has been identified and the vulnerability is not listed in CISA KEV; a vendor-released patch is available via upstream GitHub commit d7b60ff.
Server-Side Request Forgery in Animation Addons for Elementor WordPress plugin (versions before 2.7.2) permits unauthenticated remote attackers to coerce the WordPress server into issuing arbitrary HTTP requests to internal network hosts and relay the responses back to the attacker. The vulnerability stems from unsanitized user-supplied input being used directly to construct the host component of a server-side HTTP request. No public exploit or CISA KEV listing has been identified, and EPSS places exploitation probability at 0.15% (4th percentile), though SSVC notes the attack is automatable.
Server-side request forgery in Netflix Lemur's authority update path allows an authenticated user holding an authority role to redirect the Lemur backend into fetching arbitrary internal URLs, including cloud instance metadata endpoints such as 169.254.169.254. This is an incomplete-fix bypass of CVE-2026-55166 (GHSA-v2wp-frmc-5q3v): the creation-time allowlist check in `_validate_acme_url` was never applied to the `PUT /api/1/authorities/` update path, leaving the stored `acme_url` writable without re-validation. The fix is shipped in v1.9.3 with no public exploit identified at time of analysis.
Server-side request forgery in Netflix Lemur prior to 1.9.3 allows authority-role users to redirect ACME certificate issuance workflows to attacker-controlled servers, enabling JWS-signed HTTP requests to reach internal services or cloud metadata endpoints. The flaw exists in two components acting together: the PUT /api/1/authorities/ endpoint accepted acme_url modifications without revalidating the host against an allowlist, and the ACME ClientV2 blindly followed server-supplied URLs for nonce, order, authorization, and finalize operations without confirming the hostname matched the configured directory. No public exploit identified at time of analysis; vendor-released patch available in version 1.9.3.
Credential exfiltration via SSRF in AWX's GitHub webhook status callback affects Red Hat Ansible Automation Platform 2: an attacker holding admin role on a webhook-enabled job template can forge a signed GitHub pull request webhook with an arbitrary statuses_url, causing AWX to POST authenticated status updates - including the configured Git Personal Access Token in the Authorization header - to an attacker-controlled or internal endpoint. The Changed scope (S:C) in the CVSS 7.7 vector reflects that the leaked PAT extends attacker reach beyond AWX to connected Git repositories and any internal services reachable via SSRF. No public exploit identified at time of analysis, and no CISA KEV listing exists.
Server-side request forgery in the Red Hat Ansible Automation Platform 2 Controller's HashiCorp Vault credential plugin lets an authenticated user with credential-creation rights force the controller pod to leak its own Kubernetes service account token. When a HashiCorp Vault Secret Lookup credential configured for kubernetes_role authentication is tested, the kubernetes_auth() routine in awx_plugins/credentials/hashivault.py transmits the pod token to an attacker-supplied URL. With that token the attacker gains Kubernetes API access to control-plane namespaces, enabling full pod CRUD and secret reads including database credentials and the Django SECRET_KEY. No public exploit identified at time of analysis, and the flaw is not on the CISA KEV list.
Server-side request forgery in CodeWhale before 0.8.64 lets remote attackers reach internal-only IP addresses through the agent's fetch_url tool by exploiting a time-of-check-time-of-use gap in its DNS-pinning defense. Because the pre-fetch validator treated a failed DNS lookup as a pass-through ('let the HTTP request proceed and fail naturally'), an attacker who controls DNS responses can make the safety check see a non-resolving or benign answer while the real request resolves to an internal address, bypassing the SSRF allow/deny policy. No public exploit identified at time of analysis; a vendor patch and fix commit exist, and the issue was reported by VulnCheck.
Server-side request forgery in RAGFlow before v0.26.3 allows authenticated users who can create or trigger agent workflows to direct the server to make HTTP requests to arbitrary internal destinations, including RFC 1918 addresses, loopback interfaces, link-local ranges, and cloud instance metadata endpoints. The vulnerable 'Invoke' component in agent/component/invoke.py bypasses the shared assert_url_is_safe validator consistently applied in other fetch paths (crawler, SearXNG, file-upload, RSS), and returns the fetched response body directly to the caller. No public exploit has been identified at time of analysis, though two patch commits are publicly visible on GitHub and the vulnerable code location is documented in the references.
Unauthenticated SSRF in OttoKit WordPress plugin (≤1.1.35) allows any remote attacker without credentials to coerce the host server into making arbitrary outbound HTTP requests to attacker-controlled targets, including internal network resources and cloud metadata endpoints. The CVSS S:C (Scope Changed) rating confirms the vulnerability crosses security boundaries beyond the WordPress instance itself, enabling internal network reconnaissance, credential harvesting from cloud metadata services (e.g., AWS IMDSv1), or interaction with internal APIs. No active exploitation has been confirmed in CISA KEV, and no public exploit code has been identified at time of analysis.
Unauthenticated Server-Side Request Forgery in PDF Smart Viewer for Elementor (WordPress plugin by Deknows, versions up to and including 1.0.4) allows any remote, unauthenticated attacker to coerce the WordPress server into issuing arbitrary HTTP requests to attacker-controlled destinations. With a CVSS scope change (S:C), this vulnerability can be leveraged to probe and interact with internal network services not directly exposed to the internet, including cloud metadata endpoints, internal APIs, and adjacent infrastructure. No public exploit code or CISA KEV listing has been identified at time of analysis, but the zero-barrier entry (PR:N, UI:N, AC:L) makes it trivially scriptable.
Server-side request forgery in ArcadeDB before 26.8.1 enables authenticated attackers to bypass the IMPORT DATABASE command's hostname validator by exploiting a time-of-check/time-of-use gap: the validator resolves a hostname once, but the subsequent HTTP connection re-resolves it independently and follows redirects. This allows DNS rebinding or redirect-based bypass to reach cloud metadata endpoints such as the AWS IMDSv1 service, internal network services, or arbitrary local files on the host. No public exploit is identified at time of analysis, but the techniques involved are well-documented and the cloud credential exposure impact is severe on default cloud deployments.
Server-side request forgery in MLflow before 3.15.0 lets remote unauthenticated attackers coerce the server into making outbound requests to internal or cloud metadata endpoints via the POST /api/2.0/mlflow/webhooks/{id}/test endpoint. Because URL validation and the actual delivery re-resolve the hostname independently and follow redirects, an attacker can bypass the public-IP check and receive the target's response_status and response_body, enabling exfiltration of cloud credentials (e.g. from 169.254.169.254). No public exploit identified at time of analysis; the CVSS 9.3 rating and scope-change flag reflect the credential-theft potential of reaching metadata services.
Server-side request forgery in DataHub v1.5.0.1 lets a remote attacker coerce the server into fetching an attacker-supplied URL through its image-retrieval feature, with the response body and errors suppressed (blind SSRF). The reporter escalates this to arbitrary code execution, and the SSVC framework marks a proof-of-concept as available and the attack as automatable, though the flaw is not listed in CISA KEV and the EPSS probability is low at 0.24%.
Server-Side Request Forgery in Royal Elementor Addons for WordPress (versions ≤1.7.1064) allows authenticated Contributor-level users to persistently configure a malicious webhook URL via the Form Builder widget, which is then dispatched by an AJAX handler registered for both authenticated and unauthenticated callers - meaning the trigger phase requires no authentication at all. The root flaw is that wp_remote_post() is invoked on the stored URL with no host allowlist, no scheme restriction, and no private/loopback IP filtering, despite the plugin containing wpr_is_blocked_remote_host and wpr_is_private_or_local_ip helpers that are simply not called on this code path. No public exploit or CISA KEV listing has been identified at time of analysis.
Server-Side Request Forgery in Red Hat Quay's build API allows an authenticated user with repository write access to pivot into internal network segments via the Quay builder service. Exploitation requires FEATURE_BUILD_SUPPORT to be enabled and the attacker to hold at least write-level repository permissions. The CVSS vector (PR:L, C:H) reflects a meaningful but bounded threat: internal network reconnaissance and sensitive data disclosure are achievable, though no public exploit exists and EPSS sits at 0.13% (3rd percentile), indicating no observed widespread exploitation at time of analysis.
Server-side request forgery in Budibase automation steps (all versions prior to 3.41.3) exposes internal network resources - including cloud metadata endpoints, private databases, and Kubernetes APIs - to any authenticated user with automation creation rights. Five automation step types (outgoing webhook, Zapier, n8n, Slack, Discord) invoke node-fetch directly without any IP validation, completely bypassing the blacklist module that guards only the REST API integration. A second compounding flaw causes the REST API blacklist to default to an empty allowlist when the BLACKLIST_IPS environment variable is unset, meaning default Budibase deployments carry zero SSRF protection across all outbound request vectors. No CISA KEV listing exists, but the GHSA advisory provides source-level code references that substantially document the attack surface.
XXE injection in Datavane TIS v5.0.0 exposes authenticated attackers a path to SSRF and out-of-band file exfiltration against the server hosting the application. The `doEditWorkflow` endpoint accepts a `taskScript` parameter parsed by an unhardened Java `DocumentBuilderFactory` that resolves external entities and loads external DTDs, allowing a crafted XML payload to trigger outbound HTTP requests to attacker-controlled infrastructure and read local files accessible to the TIS process user, including configuration files and Derby database credentials. No public exploit has been identified at time of analysis, but VulnCheck has published a dedicated advisory and the upstream patch commit is publicly accessible, providing clear technical signal about the vulnerable code path.
DNS rebinding SSRF in Budibase before 3.40.0 exposes internal HTTP services to authenticated builder-level users who can bypass the platform's outbound fetch blacklist protections. Two distinct code paths are exploitable: the OpenAPI query import feature performs a raw fetch independently of its DNS validation guard, and the REST datasource/query execution path uses an undici dispatcher that re-resolves hostnames at connection time, defeating the pinned Node agent passed to fetchWithBlacklist(). No active exploitation is confirmed by CISA KEV, but the GHSA advisory includes detailed proof-of-concept reproduction steps with observed loopback canary responses, making this reliably reproducible by any builder-level account holder.
Server-side request forgery in Next AI Draw.io through 0.4.16 enables unauthenticated remote attackers to reach arbitrary internal HTTP services by exploiting a hostname validation bypass in the POST /api/parse-url endpoint. The validator inspects hostnames as string patterns only - without DNS resolution - allowing attackers to supply hostnames that pass the string check yet resolve to internal addresses, including cloud metadata endpoints such as the AWS IMDSv1 service. A publicly available proof-of-concept exists per VulnCheck; no CISA KEV listing has been identified at time of analysis.
Server-side request forgery in Gitea Open Source Git Server (all versions through 1.26.4) lets attackers abuse the repository migration and mirror features to reach internal network resources. Two distinct weaknesses are involved: a DNS-rebinding bypass where a hostname resolves to a permitted address during validation and to an internal address when the actual request is made, and a missing re-validation flaw where redirect or subsequent fetch targets are not re-checked against the allow/deny policy. No public exploit was identified at time of analysis, EPSS is low (0.15%), and it is not in CISA KEV, but the vendor rates technical impact as total and the issue is fixed in 1.27.0.
Unauthenticated SSRF in the Gutenverse Companion WordPress plugin (all versions through 2.5.1) allows remote unauthenticated attackers to induce the server to issue arbitrary HTTP requests to internal or external targets. The vulnerability carries a changed scope (S:C) in its CVSS vector, indicating potential for pivoting from the WordPress application layer to backend infrastructure. No public exploit code or CISA KEV listing has been identified at time of analysis, but the zero-authentication barrier makes this broadly exploitable against any unpatched WordPress installation running this plugin.
Server-side request forgery in Serendipity before 2.6.0 allows authenticated users with the adminImagesAdd permission to probe internal network services by submitting image URLs encoded as hex IPv4 addresses, IPv6 literals, or link-local ranges that bypass the serendipity_url_allowed() filter. The server fetches the internal resource and stores the response body in the publicly accessible uploads directory, enabling exfiltration of sensitive internal data such as cloud metadata or internal API responses. No public exploit or active exploitation (CISA KEV) has been identified at time of analysis, though the low attack complexity and well-understood SSRF technique lower the barrier for any attacker who obtains valid credentials.
Remote code execution and SSRF in FlowiseAI Flowise before 3.1.3 stems from a bypassable regex-based Python code validator in the CSV and Airtable Agent nodes, letting attackers smuggle malicious pandas calls through the unauthenticated prediction API via prompt injection. Because the validator blocklists rather than sandboxes, unblocked functions such as pd.read_json() can be abused to exfiltrate local datasets, reach internal services (SSRF), or execute arbitrary code. No public exploit identified at time of analysis, and it is not listed in CISA KEV; the reporting vendor VulnCheck and a GitHub Security Advisory (GHSA-w7x8-q2gp-5cgg) document the issue.
Server-Side Request Forgery in the Meeting Room Booking System (MRBS) import functionality allows remote attackers to force the application to fetch arbitrary private or local URIs, enabling potential pivot into internal networks or unauthorized integrity modification of internal services. The flaw affects all MRBS deployments prior to version 1.12.2, where the import feature accepts user-supplied URIs without restricting private address ranges or local endpoints. No public exploit code has been identified at time of analysis, but the unauthenticated network attack vector and low complexity make this trivially exploitable against internet-exposed instances.
Server-side request forgery and local file read in the OpenSearch Security Analytics plugin exposes authenticated users with low privileges as a vector for internal network reconnaissance and credential theft. The flaw resides in the threat intelligence feed parser, which fails to validate URL parameters submitted to the threat intel source configuration endpoint, allowing a crafted request to redirect server-side HTTP fetches to internal resources - including cloud metadata endpoints. Patch is confirmed available per Amazon's security bulletin AWS-2026-079; no public exploit code has been identified at time of analysis.
URLSecurityValidator SSRF bypass in compliance-trestle <= 4.0.3 allows a network-positioned attacker to reach cloud metadata services, loopback admin interfaces, and RFC 1918 internal networks by embedding IPv4-mapped IPv6 literals (e.g., [::ffff:169.254.169.254]) or the unspecified address 0.0.0.0 in OSCAL artifact import references processed by HTTPSFetcher or SFTPFetcher. Python's ipaddress module silently returns False - rather than raising TypeError - when comparing IPv6Address objects against IPv4Network ranges, so the validator's membership checks pass these forms through to requests.get unchanged. A publicly available proof-of-concept reproduces end-to-end IMDS credential exfiltration; no active exploitation is listed in CISA KEV and EPSS stands at 0.42%.
Server-side request forgery in Prowler's Lighthouse AI provider configuration allows an authenticated high-privilege user to redirect outbound HTTP requests - including the configured API key in the Authorization header - to attacker-controlled or internal network endpoints. Affected are all Prowler deployments prior to version 5.33.1 where the Lighthouse feature and an openai_compatible provider type are in use. No public exploit has been identified at time of analysis, but the attack path is straightforward for any user holding Lighthouse configuration permissions, making API key theft and internal network probing realistic objectives.
Server-Side Request Forgery in the PowerPress Podcasting plugin by Blubrry for WordPress (versions before 11.17.1) allows any authenticated Contributor-level user to supply arbitrary URLs in the Podcast Episode URL settings field, causing the server to issue unvalidated HTTP requests that can reach internal network services, cloud metadata endpoints, or other systems not directly exposed to the internet. The CVSS 7.1 score reflects high confidentiality impact against reachable internal services, and a publicly available proof-of-concept combined with a 13% EPSS score makes this an actionable priority for WordPress site operators running the plugin. No active exploitation has been confirmed in CISA KEV at time of analysis.
Server-side request forgery in Kestra's Pebble http() template function allows unauthenticated remote attackers to force the Kestra server to make outbound HTTP requests to private, loopback, or link-local addresses - including cloud Instance Metadata Service endpoints - by supplying a crafted URI inside an imported workflow flow. All Kestra releases prior to 2.0.0 are affected, with no scope restriction on reachable internal hosts, making cloud-hosted deployments particularly exposed to IAM credential theft via AWS/GCP/Azure IMDS APIs. No public exploit code or CISA KEV listing has been identified at time of analysis, but the combination of network-accessible, zero-authentication, low-complexity exploitation warrants high-priority remediation.
Privilege escalation via SSRF in Microsoft Office SharePoint exposes authenticated users to full system compromise - confidentiality, integrity, and availability all rated High. The CVSS vector (PR:L/AV:N/AC:L/UI:N) confirms that any authenticated SharePoint user can trigger the vulnerability over the network without additional complexity. No active exploitation or public exploit code has been identified at time of analysis, though the low attack complexity and broad privilege impact make this a credible near-term risk.
Server-side request forgery in Microsoft Office SharePoint enables low-privileged authenticated attackers to escalate privileges with no user interaction required, achieving high confidentiality, integrity, and availability impact. The flaw (CWE-918) allows a legitimate but low-privilege account holder to forge server-side HTTP requests, likely reaching internal administrative interfaces or credential endpoints inaccessible from the network perimeter. No public exploit code and no CISA KEV listing have been identified at time of analysis.
Server-Side Request Forgery in Apache Allura before 1.19.1 lets attackers abuse the project webhook feature to coerce the server into issuing arbitrary outbound HTTP requests, exposing internal services and cloud metadata endpoints. The flaw carries a CVSS 9.1 and is fixed in 1.19.1; it was disclosed via the Apache security team and oss-security on 2026-08-11. There is no public exploit identified at time of analysis and EPSS is low (0.20%, 11th percentile), indicating no observed weaponization yet.
SSRF in Microsoft Exchange Server enables authenticated, low-privilege network attackers to escalate privileges, with Microsoft reporting high confidentiality, integrity, and availability impact across Exchange 2016, 2019, and Subscription Edition. Vendor-released patches are available covering all affected cumulative update branches. No public exploit code exists and no active exploitation has been confirmed - EPSS sits at 0.62% (46th percentile) and CISA SSVC assigns Exploitation: none - meaning the CVSS 8.8 score outpaces current real-world threat activity.
Server-Side Request Forgery in Microsoft PowerShell Core versions 7.4.x, 7.5.x, and 7.6.x enables network-accessible unauthenticated attackers to forge outbound requests from the PowerShell process, resulting in high-impact information disclosure against resources outside the component's security boundary. The CVSS scope change (S:C) indicates that attacker-controlled SSRF requests can reach internal services inaccessible from the network perimeter, potentially exposing sensitive internal endpoints or metadata. No public exploit code has been identified at time of analysis, and active exploitation has not been confirmed by CISA KEV; Microsoft has released patched versions across all three affected branches.
Server-side request forgery with response read-back in SeaweedFS distributed storage (versions prior to 4.24) lets anyone able to reach a volume server's gRPC port coerce the server, via the unauthenticated VolumeServer.FetchAndWriteNeedle RPC, into fetching arbitrary attacker-chosen URLs and returning the response. Because the volume server gRPC plane is unauthenticated by default and the documented JWT hardening does not cover this RPC, an unauthenticated remote attacker (CVSS:3.1 AV:N/PR:N, base 9.3) can reach loopback, RFC 1918, link-local, and cloud metadata endpoints such as 169.254.169.254 to steal IAM credentials and pivot to internal services. No public exploit identified at time of analysis, and it is not in CISA KEV; the fix landed in version 4.24.
Type confusion in the Send Email node of the n8n workflow automation platform allows an attacker-supplied non-string expression value to pass uncoerced into Nodemailer, which then interprets it as a file path or URL rather than literal email content - enabling arbitrary local file disclosure and server-side request forgery (SSRF). Affected are n8n versions before 1.123.67, 2.x before 2.31.5, and 2.32.x before 2.32.1, as confirmed by GitHub Security Advisory GHSA-2x35-3fw4-9jr4. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog; exploitation depends on a specific non-default workflow configuration that requires an unauthenticated webhook, pre-configured SMTP credentials, and direct mapping of untrusted input into the email body field.
Server-Side Request Forgery in Red Hat OpenShift Container Platform 4's Dev Console webhook helpers allows authenticated users to coerce the console pod into issuing arbitrary outbound HTTP requests on their behalf. Because the console pod operates from a privileged network position within the cluster, this enables lateral movement to internal services - including the Kubernetes API server, metadata endpoints, and internal microservices - that would otherwise be unreachable from outside the cluster. No public exploit or CISA KEV listing has been identified at time of analysis, but the Scope:Changed CVSS metric reflects the cross-boundary nature of the impact.
Server-Side Request Forgery in the OpenShift Console Helm catalog proxy allows low-privileged namespace tenants to plant a malicious ProjectHelmChartRepository resource pointing to an attacker-controlled URL, causing the console pod to issue server-side fetches that bypass tenant egress restrictions. Combined with Helm catalog metadata poisoning and subsequent admin-mediated chart installation, this multi-stage attack chain enables privilege escalation within the cluster. No CISA KEV listing or public exploit code has been identified at time of analysis, though the CVSS Scope:Changed rating correctly reflects that the console pod's cross-boundary requests extend impact beyond the originating namespace.
Server-side request forgery in Pinry through 2.1.13 enables unauthenticated remote attackers to coerce the application server into issuing arbitrary HTTP requests to internal or external hosts via the pin-from-URL feature, which passes attacker-supplied URLs directly to Python's requests.get() without host allowlisting or IP validation. Because ALLOW_NEW_REGISTRATIONS defaults to true, no account or authentication is required to trigger the vulnerable endpoint, making every default-configured internet-exposed Pinry instance exploitable without any attacker preconditions. Attackers can leverage this to reach cloud metadata endpoints such as AWS IMDSv1 at 169.254.169.254, harvest IAM credentials, or probe internal services unreachable from the public internet; no public exploit has been identified at time of analysis and no CISA KEV listing is present.
Server-side request forgery in Dub's metatags edge endpoint allows unauthenticated remote attackers to direct the server to issue HTTP requests to arbitrary internal or external hosts. All Dub versions through 2026-07-10 are affected, with the root cause being the endpoint's acceptance of caller-supplied URLs without any denylist filtering or authentication requirement. Attackers can leverage this to probe RFC 1918 address space, enumerate internal services, or exfiltrate credentials from cloud metadata endpoints such as AWS IMDSv1; no public exploit code or active exploitation (CISA KEV) has been identified at time of analysis.
Unauthenticated server-side request forgery in Commvault Command Center's legacy endpoint allows a remote, unauthenticated attacker to cause the server to issue HTTP requests to arbitrary URLs, exposing internal services, cloud metadata endpoints, and credentials accessible from the Command Center's privileged network position. All versions of Commvault Cloud are indicated as affected per wildcard CPE, with Commvault releasing a resolved maintenance release per advisory CV_2026_07_5. No public exploit has been identified at time of analysis, and no CISA KEV listing is present, but the CVSS 4.0 score of 8.8 with no authentication or precondition requirements makes this a high-priority remediation target in enterprise environments.
Server-Side Request Forgery in MISP's cti-transmute tool allows unauthenticated network attackers to leverage the /fetch_misp_event and /misp_search_events endpoints as a proxy into the server's internal network by supplying a domain name whose DNS record resolves to a private or reserved IP address. The validation logic checked IP literals against blocked ranges but unconditionally trusted domain names, creating a trivially exploitable DNS-bypass gap confirmed by the upstream commit to expose full internal response bodies to anonymous callers. No public exploit has been identified and the vulnerability is not in the CISA KEV catalog, but the zero-prerequisite attack surface against potentially sensitive threat intelligence infrastructure makes prompt remediation essential.
Server-side request forgery in Grafana's mcp-grafana (Grafana MCP Server) lets an authenticated caller override the outbound request destination via the X-Grafana-URL header while using the grafana_api_request tool to control HTTP method, path, and body. Because the destination is never constrained to the configured Grafana instance, callers can pivot the server into internal, loopback, and link-local services-including cloud metadata endpoints-and read the responses. This is an incomplete-fix follow-on to CVE-2026-15583, which stopped the service-account token from leaking to unintended hosts but left the destinations themselves unrestricted; no public exploit identified at time of analysis.
Server-Side Request Forgery in usememos/memos through v0.30.0 allows authenticated users to redirect server-side HTTP requests to arbitrary internal network addresses by configuring a malicious webhook target URL. The CVSS S:C (Scope Changed) rating reflects that exploitation breaks the application boundary, enabling access to internal infrastructure such as cloud metadata endpoints, internal APIs, or RFC1918-addressed services. A publicly available proof-of-concept exists via GitHub gist; however, EPSS remains low at 0.22% (13th percentile), indicating limited observed exploitation in the wild at time of analysis despite the high CVSS score of 8.5.
Arbitrary file read and SSRF in Firecrawl before 2.11.32 lets an API caller exfiltrate files from the extraction worker and reach internal/external HTTP endpoints by abusing JSON-schema dereferencing. The extract feature passes user-supplied schemas to the json-schema-ref-parser library with default resolvers, so a $ref placed inside default, const, or enum fields (which AJV does not traverse) is resolved against the local filesystem or network; a deliberately triggered dereference error then leaks the resolved file contents back through the extraction API's persisted error message. No public exploit or CISA KEV listing is identified at time of analysis, but the fix commit ships security regression tests demonstrating the file:// and metadata-endpoint attack paths.
Server-side request forgery in gabehf/Koito through v0.3.2 lets authenticated users coerce the application server into issuing arbitrary HTTP requests to internal or external hosts via the album image endpoint. The CVSS scope-change rating (S:C) reflects that exploitation reaches beyond the vulnerable component itself - an attacker can pivot through the server to probe cloud metadata services, internal APIs, or RFC-1918 hosts unreachable directly from the internet. No public exploit or active exploitation is identified at time of analysis, but the low attack complexity and lack of URL validation make this straightforward to abuse once authenticated.
Unauthenticated SSRF in duhow/xiaoai-patch (all versions through commit fb07049) allows any remote attacker to force the Xiaomi XiaoAI smart speaker's API server to issue HTTP requests to arbitrary internal or external URLs. The /auth endpoint in api/main.py blindly accepts a user-supplied url POST parameter to redirect toward a Home Assistant instance without destination validation, enabling internal network scanning and access to internal services from the speaker's network vantage point. No public exploit code has been identified at time of analysis, and this CVE is not listed in the CISA KEV catalog.
Server-side request forgery in Automatisch through commit 41f3c56 exposes internal network services to any authenticated user holding the 'manage Flow' permission. The HTTP Request app's Custom Request action passes caller-supplied URLs directly to the backend HTTP client with no allowlist, blocklist, or redirect controls, enabling full response-body retrieval from cloud metadata endpoints, internal APIs, and private network hosts. No public exploit or CISA KEV listing has been identified at time of analysis, but the scope-changed, high-confidentiality CVSS vector reflects the severity of lateral access achievable through this single permission.
Server-Side Request Forgery in the Telefunken TE24553B45V2DZ Smart TV firmware V2.78.0.0 allows a network-adjacent unauthenticated attacker to abuse the SmartCenter browserseturl command, redirecting the device's embedded browser to loopback (127.0.0.1) and internal network destinations that are otherwise unreachable through normal browser navigation. The Vestel MB181 / Voltron181 / TiVo OS platform's SmartCenter component fails to restrict target URL schemes and destinations, enabling the TV to serve as an internal SSRF proxy against its own locally-running services. No public exploit code has been identified and this CVE is absent from the CISA KEV catalog; however, the zero-privilege, adjacent-network attack posture makes exploitation accessible to any local network attacker, including guests in hospitality deployments.
Server-side request forgery in Microsoft Office SharePoint lets a remote, unauthenticated attacker coerce the server into issuing attacker-controlled requests, enabling spoofing across a network per Microsoft's classification. The CVSS 3.1 base score is 9.6 (critical) with a changed scope, and exploitation requires a victim to interact with attacker-supplied content (UI:R). There is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Server-side request forgery in Fedify's getNodeInfo() function allows unauthenticated remote attackers to pivot through a Fedify server into internal network services - including loopback interfaces, cloud metadata endpoints (e.g., AWS IMDS at 169.254.169.254), and RFC 1918 private networks - by returning a crafted /.well-known/nodeinfo document with a malicious links[].href value. Affected versions span the 1.9 through 2.3 maintenance lines starting from 1.2.0, with response bodies from internal services returned directly to the initiating attacker. No confirmed active exploitation (not in CISA KEV) and no POC status was provided in the input data, but SSRF against cloud metadata is a high-value, well-understood attack path.