FireFighter is an incident management application. Prior to 0.0.54, the POST /api/v2/firefighter/raid/jira_bot endpoint (CreateJiraBotView) is reachable without authentication (permission_classes = [permissions.AllowAny]). Its attachments payload is fetched server-side via httpx.get() with no URL validation, then uploaded as an attachment on the Jira ticket that gets created. An unauthenticated caller able to reach the ingress can coerce the pod into fetching arbitrary URLs and exfiltrate the response as a Jira attachment. On EC2/EKS deployments that do not enforce IMDSv2, this allows theft of the temporary AWS credentials attached to the pod's IAM role. The docstring on the view claims a Bearer token is required, but the code does not enforce it. This vulnerability is fixed in 0.0.54.
### Summary
Authenticated Server-Side Request Forgery affecting the webhook trigger tools, the n8n API client (`N8N_API_URL`), and per-request URLs supplied via the `x-n8n-url` header in multi-tenant HTTP mode.
### Impact
A caller with access to the MCP session can drive HTTP requests from the n8n-mcp host to internal services and cloud metadata endpoints that the SSRF gate is meant to block. The response body is returned to the caller, making internal-service enumeration and credential theft immediate without any out-of-band channel.
- **Multi-tenant HTTP deployments** where tenants share an `AUTH_TOKEN`: any tenant with valid credentials can reach the operator's cloud metadata service and exfiltrate temporary IAM / GCP service account / Azure managed-identity credentials.
- **Single-tenant deployments**: indirect prompt injection through tool arguments reaches the same surface; an attacker who can influence the LLM's tool calls can read internal services from the n8n-mcp host.
- **Stdio deployments** are reachable via the same prompt-injection path.
### Patched Versions
Fixed in `n8n-mcp@2.50.2`.
**Note for operators:** The same SSRF gate that previously covered webhook URLs now also covers the n8n API client base URL. If `N8N_API_URL` points at `http://localhost:5678` (n8n on the same host) or an RFC1918 address (n8n on the same private network), set `WEBHOOK_SECURITY_MODE=moderate` (allows localhost, still blocks RFC1918 and cloud metadata) or `WEBHOOK_SECURITY_MODE=permissive` (allows RFC1918 too — only safe on a trusted private network). Default `strict` is correct for deployments where n8n is reachable at a public hostname.
### Workarounds
For deployments that cannot upgrade immediately:
1. **Restrict network egress** from the n8n-mcp host with a firewall, reverse proxy, or cloud security group. Explicitly deny cloud metadata IPs (`169.254.169.254`, `169.254.170.2`, `100.100.100.200`, `192.0.0.192`, and the GCP `metadata.google.internal` resolved IP) and any RFC1918 networks the server does not legitimately need to reach.
2. **Run in stdio mode** instead of HTTP if the multi-tenant surface is not needed (no shared `AUTH_TOKEN` to compromise).
3. **Disable workflow management tools** via `DISABLED_TOOLS=n8n_trigger_webhook_workflow,n8n_create_workflow,n8n_test_workflow` if the deployment does not need them.
### Credit
Reported by [@fg0x0](https://github.com/fg0x0).
CVE-2026-33975 is a high-severity Server-Side Request Forgery (SSRF) vulnerability in the open source CRM twenty (version 1.18.0 and earlier). The vulnerability arises because the SSRF protection in twenty-server's SecureHttpClientService can be bypassed using IPv4-mapped IPv6 address literals. Node.js normalizes these addresses to a hex form that the SSRF protection does not recognize, allowing an authenticated user to access internal IP addresses, including cloud metadata endpoints, potentially exfiltrating sensitive credentials such as IAM keys. No official patch or remediation guidance is currently available from the vendor.
Apache Polaris accepts literal `*` characters in namespace and table names. When it
later builds temporary S3 access policies for delegated table access, those
same characters appear to be reused unescaped in S3 IAM resource patterns
and
`s3:prefix` conditions.
In S3 IAM policy matching, `*` is treated as a wildcard rather than as
ordinary text. That means temporary credentials issued for one crafted table
can match the storage path of a different table.
In private testing against Polaris 1.4.0 using Polaris' AWS S3 temporary-
credential path on both MinIO and real AWS S3, credentials returned for
crafted tables such as `f*.t1`, `f*.*`, `*.*`, and `foo.*` could reach other
tables' S3 locations.
The confirmed behavior includes:
- reading another table's metadata control file ([Iceberg metadata JSON]);
- listing another table's exact S3 table prefix ([table prefix]);
- and, when write delegation was returned for the crafted table, creating
and
deleting an object under another table's exact S3 table prefix.
A control case using ordinary different names did not allow the same
cross-table access.
A least-privilege AWS S3 variant was also confirmed in which the attacker
principal had no Polaris permissions on the victim table and only the
minimal permissions required to create and use a crafted wildcard table
(namespace-scoped `TABLE_CREATE` and `TABLE_WRITE_DATA` on `*`). In that
setup, direct Polaris access to `foo.t1` remained forbidden, but the
attacker
could still create and load `*.*`, receive delegated S3 credentials, and use
those credentials to list, read, create, and delete objects under `foo.t1`.
In Iceberg, the metadata JSON file is a control file: it tells readers which
data files belong to the table, which snapshots exist, and which table
version
to read. So unauthorized access to it is already a meaningful
confidentiality
problem. The confirmed write-capable variant means the issue is not limited
to
disclosure.
LoLLMs WEBUI provides the Web user interface for Lord of Large Language and Multi modal Systems. A critical Server-Side Request Forgery (SSRF) vulnerability has been identified in all known existing versions of `lollms-webui`. The `@router.post("/api/proxy")` endpoint allows unauthenticated attackers to force the server into making arbitrary GET requests. This can be exploited to access internal services, scan local networks, or exfiltrate sensitive cloud metadata (e.g., AWS/GCP IAM tokens). As of time of publication, no known patched versions are available.
CKAN MCP Server is a tool for querying CKAN open data portals. Versions prior to 0.4.85 provide tools including ckan_package_search and sparql_query that accept a base_url parameter, making HTTP requests to arbitrary endpoints without restriction. A CKAN portal client has no legitimate reason to contact cloud metadata or internal network services. There is no URL validation on base_url parameter. No private IP blocking (RFC 1918, link-local 169.254.x.x), no cloud metadata blocking. The sparql_query and ckan_datastore_search_sql tools also accept arbitrary base URLs and expose injection surfaces. An attack can lead to internal network scanning, cloud metadata theft (IAM credentials via IMDS at 169.254.169.254), potential SQL/SPARQL injection via unsanitized query parameters. Attack requires prompt injection to control the base_url parameter. This issue has been fixed in version 0.4.85.
Kargo manages and automates the promotion of software artifacts. In versions 1.4.0 through 1.6.3, 1.7.0-rc.1 through 1.7.8, 1.8.0-rc.1 through 1.8.11, and 1.9.0-rc.1 through 1.9.4, the http and http-download promotion steps allow Server-Side Request Forgery (SSRF) against link-local addresses, most critically the cloud instance metadata endpoint (169.254.169.254), enabling exfiltration of sensitive data such as IAM credentials. These steps provide full control over request headers and methods, rendering cloud provider header-based SSRF mitigations ineffective. An authenticated attacker with permissions to create/update Stages or craft Promotion resources can exploit this by submitting a malicious Promotion manifest, with response data retrievable via Promotion status fields, Git repositories, or a second http step. This issue has been fixed in versions 1.6.4, 1.7.9, 1.8.12 and 1.9.5.
CVE-2026-27826 is a high-severity Server-Side Request Forgery (SSRF) vulnerability in sooperset's mcp-atlassian server versions prior to 0.17.0. It allows unauthenticated attackers who can access the HTTP endpoint to force the server to make arbitrary outbound HTTP requests by supplying two custom headers without needing an Authorization header. This vulnerability resides in the HTTP middleware and dependency injection layer, bypassing tool-level code detection. In cloud environments, it can lead to theft of IAM role credentials via the instance metadata service. In any deployment, it enables internal network reconnaissance and injection of attacker-controlled content into LLM tool results. The issue is fixed in version 0.17.0.
pathfinding.cloud is a newly introduced online library that catalogs AWS IAM privilege escalation paths, providing detailed mappings of how attackers might exploit misconfigurations or overly permissive policies to escalate privileges within AWS environments. While not a vulnerability itself, this resource can aid attackers in identifying and exploiting weaknesses in AWS IAM configurations. European organizations using AWS cloud services could face increased risk of privilege escalation attacks if their IAM policies are not properly secured. The threat is medium severity due to the potential impact on confidentiality and integrity, ease of exploitation given misconfigurations, and the broad use of AWS in Europe. Mitigation requires rigorous IAM policy audits, least privilege enforcement, continuous monitoring, and use of automated tools to detect privilege escalation paths. Countries with high AWS adoption and critical cloud infrastructure, such as Germany, the UK, France, and the Netherlands, are most likely to be affected. Defenders should prioritize reviewing IAM roles, permissions boundaries, and trust relationships to prevent abuse. This resource emphasizes the importance of proactive cloud security hygiene to reduce attack surface and privilege escalation risks.
A large-scale cryptomining campaign is leveraging compromised AWS IAM credentials to illicitly mine cryptocurrency. Attackers gain unauthorized access to AWS accounts by exploiting stolen or leaked IAM credentials, enabling them to deploy and run crypto mining workloads in the cloud environment. This results in increased cloud resource consumption, unexpected costs, and potential degradation of legitimate services. The campaign is ongoing and has been recently reported by a trusted cybersecurity news source, highlighting its high priority. No known public exploits or patches are currently associated with this campaign. European organizations using AWS cloud services are at risk, especially those with inadequate IAM credential management and monitoring. Attackers do not require user interaction once credentials are compromised, making the threat easier to exploit. Mitigation requires stringent IAM credential hygiene, continuous monitoring for anomalous cloud activity, and rapid incident response to unauthorized resource usage. Countries with significant AWS adoption and critical cloud infrastructure are more likely to be targeted. The threat severity is assessed as high due to the potential financial impact, ease of exploitation, and broad scope of affected systems.
The Coupang data breach was caused by a former employee who retained unauthorized system access after leaving the company. This insider threat led to a high-severity data breach compromising sensitive information. Although no known exploits are currently active in the wild, the breach highlights significant gaps in access revocation and internal security controls. European organizations should be vigilant about insider threats and ensure strict offboarding procedures. The breach primarily affects companies with similar access management challenges and those operating in e-commerce or data-sensitive sectors. Countries with strong e-commerce markets and data privacy regulations, such as Germany, France, and the UK, are particularly at risk. Mitigation requires immediate review and enforcement of identity and access management (IAM) policies, continuous monitoring for anomalous access, and comprehensive employee offboarding protocols. Given the ease of exploitation via retained access and the potential exposure of confidential data, the severity is assessed as high. Defenders must prioritize internal security hygiene to prevent similar incidents.
A vulnerability has been identified in COMOS V10.6 (All versions < V10.6.1), COMOS V10.6 (All versions < V10.6.1), NX V2412 (All versions < V2412.8700), NX V2506 (All versions < V2506.6000), Simcenter 3D (All versions < V2506.6000), Simcenter Femap (All versions < V2506.0002), Solid Edge SE2025 (All versions < V225.0 Update 10), Solid Edge SE2026 (All versions < V226.0 Update 1). The IAM client in affected products is missing server certificate validation while establishing TLS connections to the authorization server. This could allow an attacker to perform a man-in-the-middle attack.
Typebot is an open-source chatbot builder. In versions prior to 3.13.1, a Server-Side Request Forgery (SSRF) vulnerability in the Typebot webhook block (HTTP Request component) functionality allows authenticated users to make arbitrary HTTP requests from the server, including access to AWS Instance Metadata Service (IMDS). By bypassing IMDSv2 protection through custom header injection, attackers can extract temporary AWS IAM credentials for the EKS node role, leading to complete compromise of the Kubernetes cluster and associated AWS infrastructure. Version 3.13.1 fixes the issue.
CVE-2025-10853 is a reflected cross-site scripting (XSS) vulnerability in the management console of WSO2 Open Banking IAM version 2.0.0. It arises from improper output encoding of user-supplied input, allowing attackers to inject arbitrary JavaScript via manipulated parameters. Exploitation can lead to UI manipulation, redirection to malicious sites, or theft of browser data. Although session cookies are protected with the httpOnly flag, reducing session hijacking risks, the vulnerability still poses confidentiality and integrity concerns. The CVSS score is 5.2 (medium severity), reflecting the need for user interaction and the attack vector being adjacent network. No known exploits are currently in the wild. European organizations using WSO2 Open Banking IAM should prioritize patching and input validation to mitigate risks.
Recent data analysis from AWS highlights that the majority of cloud breaches stem from compromised credentials and misconfigurations within cloud environments. These issues primarily involve improper management of access keys, overly permissive IAM roles, and unsecured storage buckets. European organizations relying on AWS cloud services are at risk of unauthorized access, data leakage, and service disruption if such vulnerabilities are present. The threat does not involve a specific exploit but reflects a widespread security posture problem. Mitigation requires rigorous credential management, least privilege enforcement, continuous configuration auditing, and automated detection of anomalies. Countries with high AWS adoption and significant cloud infrastructure usage, such as Germany, the UK, France, and the Netherlands, are particularly vulnerable. Given the ease of exploitation through stolen credentials and the broad impact on confidentiality and availability, the severity is assessed as high. Defenders should prioritize identity and access management hygiene and cloud security posture management to reduce exposure.
OpenBao's AWS Plugin generates AWS access credentials based on IAM policies. Prior to version 0.1.1, the AWS Plugin is vulnerable to cross-account IAM role Impersonation in the AWS auth method. The vulnerability allows an IAM role from an untrusted AWS account to authenticate by impersonating a role with the same name in a trusted account, leading to unauthorized access. This impacts all users of the auth-aws plugin who operate in a multi-account AWS environment where IAM role names may not be unique across accounts. This vulnerability has been patched in version 0.1.1 of the auth-aws plugin. A workaround for this issue involves guaranteeing that IAM role names are unique across all AWS accounts that could potentially interact with your OpenBao environment, and to audit for any duplicate IAM roles.
Over the past few weeks, Rapid7 has observed increased activity of a new threat group attacking AWS cloud environments with the goal of data exfiltration and subsequent extortion of the victim. This threat group refers to itself as ‘Crimson Collective’ and has recently announced that it is behind an attack on Red Hat, wherein it claims to have stolen private repositories from Red Hat’s GitLab.
Vasion Print (formerly PrinterLogic) Virtual Appliance Host prior to version 25.1.102 and Application prior to version 25.1.1413 (VA/SaaS deployments) contain a protection mechanism failure vulnerability within the file_get_contents() function. When an administrator configures a printer’s hostname (or similar callback field), the value is passed unchecked to PHP’s file_get_contents()/cURL functions, which follow redirects and impose no allow‑list, scheme, or IP‑range restrictions. An admin‑level attacker can therefore point the hostname to a malicious web server that issues a 301 redirect to internal endpoints such as the AWS EC2 metadata service. The server follows the redirect, retrieves the metadata, and returns or stores the credentials, enabling the attacker to steal cloud IAM keys, enumerate internal services, and pivot further into the SaaS infrastructure. This vulnerability has been confirmed to be remediated, but it is unclear as to when the patch was introduced.
A cross-tenant authentication vulnerability exists in multiple WSO2 products due to improper cryptographic design in Adaptive Authentication. A single cryptographic key is used across all tenants to sign authentication cookies, allowing a privileged user in one tenant to forge authentication cookies for users in other tenants.
Because the Auto-Login feature is enabled by default, this flaw may allow an attacker to gain unauthorized access and potentially take over accounts in other tenants. Successful exploitation requires access to Adaptive Authentication functionality, which is typically restricted to high-privileged users. The vulnerability is only exploitable when Auto-Login is enabled, reducing its practical impact in deployments where the feature is disabled.