Skip to main content
VulnerabilityPublished

CVE-2026-82044: UTMStack before 11.2.16 contains a server-side request forgery vulnerability that allows authenticated attackers to make the server request

Affects UTMStackSource GCVE Database

0
Compare

Not known to be exploited · CVSS 7.7 High : upgrade to 11.2.16 soon.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
7.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 17% 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:H/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 or required beyond applying the official patch.

Description

UTMStack versions prior to 11.2.16 contain a server-side request forgery (SSRF) vulnerability. Authenticated attackers can exploit this flaw by supplying an unvalidated URL parameter to the PdfService.downloadPdf() method via the GET /api/generate-pdf-report endpoint. This allows the attacker to make the server request arbitrary internal resources, potentially exposing sensitive internal data rendered into the generated PDF report.

References

Community reviews

Loading reviews…