Skip to main content
Vulnerability Database/CVE-2026-82040

CVE-2026-82040: UTMStack SSRF Vulnerability

CVE-2026-82040 is a server-side request forgery flaw in UTMStack allowing authenticated attackers to make the server send requests to arbitrary internal or cloud metadata hosts. This article covers the technical details, affected versions, impact assessment, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-82040 Overview

CVE-2026-82040 is a Server-Side Request Forgery (SSRF) vulnerability in UTMStack versions before 11.2.16. The flaw resides in the IdentityProviderService.validateMetadataUrl() method, which fails to validate the host, IP address, or scheme of a user-supplied metadata URL. Authenticated attackers can abuse the POST/PUT /api/identity-providers endpoint to force the UTMStack server to issue arbitrary outbound HTTP requests. This behavior enables internal network port scanning and access to cloud instance-metadata services such as AWS IMDS. The weakness is classified under CWE-918.

Critical Impact

Authenticated attackers can pivot through the UTMStack server to reach internal network hosts and cloud metadata endpoints, potentially harvesting cloud credentials from instance metadata services.

Affected Products

  • UTMStack versions prior to 11.2.16
  • UTMStack backend IdentityProviderService component
  • UTMStack identity-providers API (/api/identity-providers)

Discovery Timeline

  • 2026-10-02 - CVE-2026-82040 published to NVD
  • 2026-10-06 - Last updated in NVD database
  • UTMStack v11.2.16 - Vendor released patched version addressing seven disclosed CVEs (82039-82045)

Technical Details for CVE-2026-82040

Vulnerability Analysis

The vulnerability exists in the validateMetadataUrl() method within IdentityProviderService.java. When an authenticated user submits an identity provider configuration, the service fetches the SAML or OIDC metadata document from the supplied URL. The pre-patch implementation accepts any URL without filtering the destination host, resulting in classic SSRF behavior.

An attacker with low-privilege authenticated access can supply URLs targeting localhost, RFC1918 ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), or cloud metadata endpoints such as http://169.254.169.254/latest/meta-data/. The server-side HTTP client then issues the request from the UTMStack host, bypassing network perimeter controls.

Response differences, timing variations, and error messages allow the attacker to enumerate reachable internal services and open ports. In cloud deployments, successful retrieval of IAM role credentials from the instance-metadata service enables lateral movement into the cloud account.

Root Cause

The root cause is missing input validation on the metadataUrl parameter. The pre-patch code did not perform scheme allow-listing (HTTP/HTTPS only), hostname resolution checks, or IP address filtering to block loopback, link-local, and private address ranges. The vendor patch adds imports for java.net.InetAddress, java.net.UnknownHostException, and java.util.Set, indicating introduction of host resolution and deny-list enforcement.

Attack Vector

Exploitation requires an authenticated session with permission to create or update identity providers. The attacker sends a crafted POST or PUT request to /api/identity-providers containing a metadataUrl field pointing to an internal target. The UTMStack backend fetches the URL and returns observable behavior to the attacker through API response content, status codes, or timing.

java
// Patch diff from IdentityProviderService.java
 import java.io.IOException;
 import java.net.HttpURLConnection;
+import java.net.InetAddress;
 import java.net.MalformedURLException;
+import java.net.UnknownHostException;
 import java.net.URL;
 import java.time.LocalDateTime;
 import java.util.Optional;
+import java.util.Set;

 @Service
 @RequiredArgsConstructor
// Source: https://github.com/utmstack/UTMStack/commit/4e7a727c3b8d8e2ad020d3b4f982a6d085dbecdd

The added imports confirm the fix introduces DNS resolution via InetAddress and a Set-based deny-list of restricted address ranges to block SSRF targets.

Detection Methods for CVE-2026-82040

Indicators of Compromise

  • Outbound HTTP connections from the UTMStack backend to RFC1918 addresses, 127.0.0.0/8, or 169.254.169.254
  • Unexpected POST or PUT requests to /api/identity-providers from low-privilege user accounts
  • Identity provider records containing metadataUrl values pointing to non-public hosts
  • UTMStack application logs showing validateMetadataUrl() invocations against internal IPs

Detection Strategies

  • Inspect UTMStack audit logs for identity-provider creation and update events referencing internal, loopback, or link-local destinations
  • Correlate authenticated API sessions with egress traffic from the UTMStack host to atypical internal destinations
  • Alert on any process on the UTMStack server making requests to cloud metadata IP 169.254.169.254

Monitoring Recommendations

  • Enable verbose request logging on the identity-providers endpoint and forward to a central SIEM
  • Baseline normal outbound destinations from the UTMStack backend and alert on deviations
  • Monitor cloud provider audit logs (AWS CloudTrail, Azure Activity Log) for unexpected use of the UTMStack instance role

How to Mitigate CVE-2026-82040

Immediate Actions Required

  • Upgrade UTMStack to version 11.2.16 or later, which contains the vendor fix for CVEs 82039 through 82045
  • Audit existing identity provider configurations and remove entries referencing internal or metadata hosts
  • Rotate any cloud IAM credentials associated with the UTMStack host if SSRF activity is suspected

Patch Information

The fix is included in UTMStack Release v11.2.16 and implemented in commit 4e7a727. The commit adds host validation logic to IdentityProviderService.validateMetadataUrl() using InetAddress resolution and a deny-list of restricted address ranges. See the Vulncheck SSRF Advisory for full disclosure details.

Workarounds

  • Restrict access to the /api/identity-providers endpoint using an upstream reverse proxy or WAF rule until patching is possible
  • Apply egress filtering on the UTMStack host to block outbound traffic to RFC1918 ranges, 127.0.0.0/8, and 169.254.169.254
  • On AWS deployments, enforce IMDSv2 with session tokens and set a low hop limit to prevent SSRF-based credential theft
  • Limit identity provider management privileges to a minimal set of trusted administrators
bash
# Example iptables egress rule blocking cloud metadata access from UTMStack host
iptables -A OUTPUT -d 169.254.169.254 -j DROP
iptables -A OUTPUT -d 127.0.0.0/8 ! -o lo -j DROP
iptables -A OUTPUT -d 10.0.0.0/8 -m owner --uid-owner utmstack -j DROP

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.