Skip to main content
VulnerabilityPublished

CVE-2026-82040: UTMStack before 11.2.16 contains a server-side request forgery vulnerability in IdentityProviderService.validateMetadataUrl() that allows

Affects UTMStackSource GCVE Database

0
Compare

Not known to be exploited · CVSS 5.0 Medium : upgrade to 11.2.16 when convenient.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
5.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 11.2.16
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade utmstack/UTMStack to 11.2.16.

Affected software

ProductAffectedFixed in
GitHubutmstack/UTMStackpkg:github/utmstack/UTMStackOther threatsAffected
  • <11.2.16
Fixed in
  • 11.2.16

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in UTMStack version 11.2.16. Users should upgrade to version 11.2.16 or later to remediate this vulnerability. No additional mitigation guidance is provided in the vendor advisory; therefore, upgrading is the recommended action.

Description

UTMStack versions prior to 11.2.16 have a server-side request forgery (SSRF) vulnerability in the IdentityProviderService.validateMetadataUrl() function. This flaw allows authenticated attackers to supply a malicious metadata URL to the identity-providers endpoint, causing the server to send requests to arbitrary internal or cloud metadata hosts. The vulnerability affects the POST/PUT /api/identity-providers endpoint, which does not validate the target host, IP address, or URL scheme. Exploitation can enable internal network port scanning and access to cloud instance-metadata services.

References

Community reviews

Loading reviews…