Is CVE-2026-82040 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-82040 being exploited in the wild.

How severe is CVE-2026-82040?

Medium severity, with a CVSS score of 5, published 2 October 2026.

Is there a fix for CVE-2026-82040?

Yes: fixed in 11.2.16. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-82040 attacked?

It is attacked over the network.

Am I affected by CVE-2026-82040?

Check whether you run UTMStack at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-82040: UTMStack server-side request forgery in IdentityProviderService

CVE-2026-82040 · Severity: medium · CVSS 5 · Published 2026-10-02

UTMStack is a security information and event management platform used to monitor and analyze security events across networks and cloud environments. Authenticated attackers can exploit a flaw in the identity provider metadata URL validation to trick the server into making requests to arbitrary internal hosts or cloud metadata services. This could allow attackers to discover internal network topology, access cloud credentials, or perform port scanning without direct network access.

Technologies: UTMStack. Vendors: UTMStack.

Quick answers

Is CVE-2026-82040 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-82040 being exploited in the wild.
How severe is CVE-2026-82040?: Medium severity, with a CVSS score of 5, published 2 October 2026.
Which products and versions are affected?: UTMStack before 11.2.16.
Is there a fix for CVE-2026-82040?: Yes: fixed in 11.2.16. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-82040 attacked?: It is attacked over the network.
Am I affected by CVE-2026-82040?: Check whether you run UTMStack at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 11.2.16

Technical details

The IdentityProviderService.validateMetadataUrl() method in UTMStack before 11.2.16 fails to properly validate metadata URLs supplied to the POST/PUT /api/identity-providers endpoint, allowing authenticated attackers to perform server-side request forgery (SSRF). The vulnerability permits requests to internal IP addresses, loopback ranges, and cloud instance-metadata services by bypassing host, IP, and scheme validation. The fix restricts IdP metadata URLs to http(s) public hosts, rejects literal IP addresses, loopback/site-local/link-local ranges, and disables HTTP redirects.

Affected products

UTMStack UTMStack before 11.2.16

Timeline

2026-10-02: disclosed
2026-10-01: patched: Release v11.2.16 published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.