CVE-2026-82044

waiting for further signalsZero needs more public information before it can validate it.

GHSA-hg4r-wjvj-4cww ↗EUVD-2026-91799 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
UTMStack < 11.2.16
fixed in 11.2.16
ETK-2026-398, permanent identifier
18d 17h 04msince last run
1h 00mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+6h22m
0
+2h
+4h
+8h
+10h
+12h

description

UTMStack releases before 11.2.16 are affected by a server-side request forgery issue in PDF report generation. An authenticated user may cause the PDF service to retrieve internal resources, potentially exposing their contents in a generated PDF.

mitigation

Upgrade UTMStack to version 11.2.16 or later.

fixed in 11.2.16

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.26%16th percentile
agent run time
1h 00m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-02 20:20Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-02 20:20Z
    ghsa: trigger signal, started the run
  2. 2026-10-02 20:20Z

this entry in the feed

GET /api/v1/feed/CVE-2026-82044

{
  "etk_id": "ETK-2026-398",
  "cve_id": "CVE-2026-82044",
  "display_id": "CVE-2026-82044",
  "ghsa_id": "GHSA-hg4r-wjvj-4cww",
  "euvd_id": "EUVD-2026-91799",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Server-side request forgery in UTMStack PDF report generation",
  "summary": "UTMStack releases before 11.2.16 are affected by a server-side request forgery issue in PDF report generation. An authenticated user may cause the PDF service to retrieve internal resources, potentially exposing their contents in a generated PDF.",
  "mitigation": "Upgrade UTMStack to version 11.2.16 or later.",
  "vendor": "UTMStack",
  "product": "UTMStack",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 11.2.16"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "11.2.16"
      ],
      "package_name": "UTMStack",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N",
  "epss_score": 0.0026,
  "epss_percentile": 0.162,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 60.29290151666667,
  "t0_at": "2026-10-02T20:20:47.694000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-02T20:20:47.694000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T20:20:47.694000+00:00",
      "url": "https://github.com/advisories/GHSA-hg4r-wjvj-4cww"
    }
  }
}

published 2026-10-03 01:42Z
last change 2026-10-21 18:49Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.