CVE-2026-129137

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

GHSA-3qm5-67jg-9m3r ↗EUVD-2026-125777 ↗

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 PowerShell Universal < 2026.3.5
fixed in 2026.3.5
CWE-276 Incorrect Default Permissions
ETK-2026-4430Zero's internal tracking ID, independent of the CVE number., permanent identifier
10h 06msince last run
17mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h21m
+2h
+4h
+6h
+8h
+10h
+12h

description

Devolutions PowerShell Universal 2026.3.4 and earlier use unsafe default permissions for the agent configuration folder. A local unprivileged user who can modify that configuration may cause code to run as SYSTEM.

mitigation

Upgrade PowerShell Universal to version 2026.3.5 or later. Restrict write access to the agent configuration folder to trusted administrative accounts.

fixed in 2026.3.5

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.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
17m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-13 21:22Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-13 21:22Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4430",
  "cve_id": "CVE-2026-129137",
  "display_id": "CVE-2026-129137",
  "ghsa_id": "GHSA-3qm5-67jg-9m3r",
  "euvd_id": "EUVD-2026-125777",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Agent configuration permission flaw in PowerShell Universal",
  "summary": "Devolutions PowerShell Universal 2026.3.4 and earlier use unsafe default permissions for the agent configuration folder. A local unprivileged user who can modify that configuration may cause code to run as SYSTEM.",
  "mitigation": "Upgrade PowerShell Universal to version 2026.3.5 or later. Restrict write access to the agent configuration folder to trusted administrative accounts.",
  "vendor": "Devolutions",
  "product": "PowerShell Universal",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 2026.3.5"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2026.3.5"
      ],
      "package_name": "PowerShell Universal",
      "purl": null
    }
  ],
  "cwes": [
    276
  ],
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 17.1866873,
  "t0_at": "2026-11-13T21:22:47.164000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-13T21:22:47.164000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-13T21:22:47.164000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-129137"
    }
  }
}

published 2026-11-13 21:26Z
last change 2026-11-14 06:33Z

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.