AIL Framework versions before 7.0 contain a server-side request forgery (SSRF) vulnerability in the crawler submission feature. Authenticated users with low privileges can submit arbitrary URLs for crawling without sufficient validation, allowing requests to internal or restricted network addresses. This includes localhost, private IP ranges, link-local addresses, and cloud metadata services. The vulnerability enables attackers to use the server as a pivot to access internal services and retrieve sensitive data such as HTML content, screenshots, and HAR data. A patch has been introduced to validate and reject URLs resolving to non-global IP addresses, mitigating this risk.
Animation Addons for Elementor WordPress plugin versions before 2.7.2 contain a server-side request forgery (SSRF) vulnerability. This flaw allows unauthenticated users to supply a value that is used to build the host of a server-side HTTP request without proper validation. Exploiting this vulnerability enables attackers to make the site send requests to internal hosts and read the responses.
CVE-2026-65985 is a Server-Side Request Forgery (SSRF) vulnerability in frangoteam's FUXA software, versions 1.3.2 and earlier. It allows an authenticated non-admin runtime user to manipulate the device-webapi-request handler to make the server issue arbitrary HTTP or HTTPS requests. The vulnerability is fixed in version 1.3.3.
CVE-2026-47719 is a Server-Side Request Forgery (SSRF) vulnerability in frangoteam's FUXA software, a web-based SCADA/HMI/Dashboard tool. Versions prior to 1.3.2 allow unauthenticated remote attackers to make the server perform HTTP(S) requests to arbitrary destinations by exploiting insufficient authorization checks in Socket.IO handlers. This can expose sensitive internal resources such as cloud metadata, administrative services, industrial endpoints, and ODBC data accessible from the FUXA host. The vulnerability is fixed in version 1.3.2.
A Server-Side Request Forgery (SSRF) vulnerability exists in Netflix Lemur prior to version 1.9.3. An authority-role member could update the acme_url without revalidation, allowing redirection of ACME client requests to attacker-controlled servers. This flaw enables the Lemur client to follow URLs from malicious ACME servers, potentially sending signed requests to internal or cloud metadata endpoints. The vulnerability requires authority-level access but not global administrator privileges. The issue is fixed in Lemur version 1.9.3 by enforcing host validation during the ACME flow.
Lemur manages TLS certificate creation. Prior to 1.9.3, _validate_acme_url enforced ACME_DIRECTORY_HOST_ALLOWLIST when an authority was created, but PUT /api/1/authorities/ passed options to lemur/authorities/service.py without applying the same check. A user holding an authority role could replace the stored acme_url with an internal service or instance-metadata URL such as 169.254.169.254. The next issuance operation loaded that value and passed it to ClientV2.get_directory, causing an outbound request from the Lemur backend. This bypassed the creation-time mitigation for CVE-2026-55166 and could expose internal services or cloud metadata. The fix revalidates acme_url whenever authority options are updated. This issue is fixed in version 1.9.3.
A time-of-check to time-of-use (TOCTOU) race condition vulnerability exists in Netflix's Lemur TLS certificate management tool prior to version 1.9.3. The vulnerability involves the _validate_revocation_url function, which fails to properly validate HTTP redirect targets during CRL and OCSP URL checks, allowing attacker-controlled URLs to redirect to internal or sensitive network addresses. This can lead to blind internal requests triggered by certificate uploads. The issue is fixed in Lemur version 1.9.3 by disabling redirects and pinning validated addresses.
A Server-Side Request Forgery (SSRF) vulnerability exists in Netflix Lemur versions prior to 1.9.2. The vulnerability arises because Lemur accepts CRL Distribution Point and OCSP responder URLs from uploaded certificate extensions without proper validation. An authenticated operator could exploit this by submitting a crafted certificate to cause internal network requests to loopback, RFC1918, link-local, or instance metadata IP addresses. This could allow probing of internal services and unintended side effects from the Lemur host. Additionally, the CRL cache was unbounded, enabling memory consumption via attacker-controlled entries. The issue is fixed in Lemur version 1.9.2.
CVE-2026-55166 is a critical improper authorization vulnerability in Netflix Lemur versions prior to 1.9.2. Authenticated users could manipulate the ACME authority URL without proper server-side restrictions, enabling server-side request forgery (SSRF) to internal cloud services and metadata endpoints. Additionally, authorization flaws could allow continued access to private certificate key material after ownership or role changes, with insufficient audit logging to detect such access. The vulnerability could lead to exposure of cloud credentials and long-lived private keys. The issue is fixed in Lemur version 1.9.2 by adding host allowlist validation and improving audit context for key exports.
CVE-2026-50143 is a Server-Side Request Forgery (SSRF) vulnerability in the apify-mcp-server prior to version 0.10.11. It allows a malicious Actor publisher to manipulate URLs to redirect requests to third-party hosts, exposing the victim's Apify API token and enabling unauthorized access to Actors, stored data, and billable compute. The vulnerability is fixed in version 0.10.11.
MobSF is a mobile application security testing tool used. Prior to 4.5.1, get_browsable_activities in mobsf/StaticAnalyzer/views/android/manifest_analysis.py validates only an Android manifest android:host value with valid_host before appending a separately supplied android:port to the URL fetched by _check_url, allowing an authenticated user to upload a crafted APK that makes requests to an attacker-selected nonstandard port at /.well-known/assetlinks.json. With an attacker-controlled hostname and DNS rebinding between validation and the requests.get connection, the request can reach an internal service, although redirects remain disabled and the path is fixed. This issue is fixed in version 4.5.1.
MagicMirror² versions prior to 2.37.0 contain a Server-Side Request Forgery (SSRF) vulnerability in the newsfeed module. The vulnerability arises because the checkArticleUrl function accepts URLs via an unauthenticated Socket.IO namespace and performs HTTP HEAD requests without validating the URL. This allows attackers to probe internal hosts and ports and potentially trigger side effects on services responding to HEAD requests. The issue is resolved in version 2.37.0.
MagicMirror² versions prior to 2.37.0 contain a server-side request forgery (SSRF) vulnerability in the ADD_CALENDAR handler of the calendar module. This handler accepts attacker-controlled URLs and authentication data via an unauthenticated Socket.IO namespace, allowing SSRF without proper validation. The vulnerability can lead to exfiltration of internal service response data if the response is a valid iCal calendar. The issue is fixed in version 2.37.0.
CVE-2026-71365 is a server-side request forgery (SSRF) vulnerability in Red Hat Ansible Automation Platform 2.5 for RHEL 8. It arises from AWX's webhook status callback mechanism, which does not validate the target host of the status callback URL extracted from GitHub pull request webhooks. An admin user on a webhook-enabled job template can exploit this to leak the Git Personal Access Token (PAT) by causing AWX to send authenticated status updates to an attacker-controlled or internal URL.
A flaw was found in the AAP Controller's HashiCorp Vault credential plugin. The kubernetes_auth() function in awx_plugins/credentials/hashivault.py reads the controller pod's Kubernetes service account token and sends it to an attacker-controlled URL when a HashiCorp Vault Secret Lookup credential with kubernetes_role authentication is tested. An authenticated attacker with credential-creation privileges can exfiltrate the service account token, gaining Kubernetes API access to the control plane namespaces with full pod CRUD and secret read permissions, including database credentials and the Django SECRET_KEY.
Apache SkyWalking MCP version 0.1.0 contains a critical Server-Side Request Forgery (SSRF) vulnerability and a GraphQL expression injection issue. These vulnerabilities allow an attacker to manipulate server requests and inject malicious GraphQL expressions. The issue is fixed in version 0.2.0, which users are advised to upgrade to.
MLflow versions from 3.3.0 up to but not including 3.15.0 contain a server-side request forgery (SSRF) vulnerability in the unauthenticated POST /api/2.0/mlflow/webhooks/{id}/test endpoint. The vulnerability arises because the URL validation only checks the original URL, but the webhook delivery process follows redirects and re-resolves hostnames without pinning the validated address. This allows attackers to make requests to internal or cloud metadata services and obtain response data. The issue is fixed in version 3.15.0.