CVE-2026-110804

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

GHSA-jhmq-jch2-cv3p ↗EUVD-2026-102876 ↗

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.
Devolutions Server < 2026.3.10
fixed in 2026.3.10
CWE-915 Improperly Controlled Modification of Dynamically-Determined Object Attributes
ETK-2026-2251Zero's internal tracking ID, independent of the CVE number., permanent identifier
3h 05msince last run
38mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+107h24m
0
+2h
+4h
+6h
+8h
+10h

description

Devolutions Server versions through 2026.3.8.0 can accept improperly controlled JIT elevation settings during PAM checkout updates. An authenticated user with PAM checkout access may be able to preserve elevated access or remove Active Directory groups.

mitigation

Upgrade Devolutions Server to version 2026.3.10. Limit PAM checkout access to trusted users until the update is complete.

fixed in 2026.3.10

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.
–
agent run time
38m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-16 13:45Z
Δ 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-16 13:45Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2251",
  "cve_id": "CVE-2026-110804",
  "display_id": "CVE-2026-110804",
  "ghsa_id": "GHSA-jhmq-jch2-cv3p",
  "euvd_id": "EUVD-2026-102876",
  "status": "published",
  "anchor_state": "anchored",
  "title": "JIT elevation setting manipulation in Devolutions Server PAM checkout",
  "summary": "Devolutions Server versions through 2026.3.8.0 can accept improperly controlled JIT elevation settings during PAM checkout updates. An authenticated user with PAM checkout access may be able to preserve elevated access or remove Active Directory groups.",
  "mitigation": "Upgrade Devolutions Server to version 2026.3.10. Limit PAM checkout access to trusted users until the update is complete.",
  "vendor": "Devolutions",
  "product": "Server",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 2026.3.10"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2026.3.10"
      ],
      "package_name": "Server",
      "purl": null
    }
  ],
  "cwes": [
    915
  ],
  "cvss_score": 4.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 37.5348098,
  "t0_at": "2026-10-16T13:45:38.143000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-16T13:45:38.143000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-16T13:45:38.143000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-110804"
    }
  }
}

published 2026-10-21 00:31Z
last change 2026-10-21 03:59Z

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.