CVE-2026-82042

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

GHSA-phx4-fx7q-vfw9 ↗EUVD-2026-91797 ↗

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
CWE-306 Missing Authentication for Critical Function
ETK-2026-374, permanent identifier
18d 20h 34msince last run
53mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+5h01m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

UTMStack versions before 11.2.16 may accept a configured internal API key as authorization for administrative API requests. An attacker who obtains that key can access administrative functions without a user account or JWT.

mitigation

Upgrade UTMStack to version 11.2.16 or later. Until the upgrade is complete, restrict exposure of the administrative API and rotate the configured internal key if its confidentiality is uncertain.

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.55%44th percentile
agent run time
53m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-02 20:15Z
Δ 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:15Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-374",
  "cve_id": "CVE-2026-82042",
  "display_id": "CVE-2026-82042",
  "ghsa_id": "GHSA-phx4-fx7q-vfw9",
  "euvd_id": "EUVD-2026-91797",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authentication bypass in UTMStack internal API key handling",
  "summary": "UTMStack versions before 11.2.16 may accept a configured internal API key as authorization for administrative API requests. An attacker who obtains that key can access administrative functions without a user account or JWT.",
  "mitigation": "Upgrade UTMStack to version 11.2.16 or later. Until the upgrade is complete, restrict exposure of the administrative API and rotate the configured internal key if its confidentiality is uncertain.",
  "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": [
    306
  ],
  "cvss_score": 9.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.0055,
  "epss_percentile": 0.4496,
  "epss_asof": "2026-10-21",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 52.8443314,
  "t0_at": "2026-10-02T20:15:27.035000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-02T20:15:27.035000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T20:15:27.035000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-82042"
    }
  }
}

published 2026-10-02 21:08Z
last change 2026-10-21 21:36Z

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.