CVE-2026-125882

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

GHSA-x4hh-6ghj-wrvg ↗EUVD-2026-122963 ↗

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.+7d
N-able N-central < 26.4.1
fixed in 26.4.1
ETK-2026-4695Zero's internal tracking ID, independent of the CVE number., permanent identifier
3h 11msince last run
12mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
cve.org publicationtrigger signal +6.1dkev+7.0dwaiting for further signals+7.9d
0
+2d
+4d
+6d

description

N-able N-central versions earlier than 26.4.1 are affected by a relative path traversal vulnerability. An attacker may be able to access unintended filesystem paths; the evidence does not specify authentication or endpoint preconditions.

mitigation

Upgrade N-central to version 26.4.1 or later.

fixed in 26.4.1

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, high privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.55%46th percentile
agent run time
12m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-10 21:25Z
Δ 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.
+7d

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-10 21:25Z
  2. 2026-11-17
    vulncheck_kev: trigger signal, started the run
  3. 2026-11-17 00:00Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4695",
  "cve_id": "CVE-2026-125882",
  "display_id": "CVE-2026-125882",
  "ghsa_id": "GHSA-x4hh-6ghj-wrvg",
  "euvd_id": "EUVD-2026-122963",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Relative path traversal in N-central",
  "summary": "N-able N-central versions earlier than 26.4.1 are affected by a relative path traversal vulnerability. An attacker may be able to access unintended filesystem paths; the evidence does not specify authentication or endpoint preconditions.",
  "mitigation": "Upgrade N-central to version 26.4.1 or later.",
  "vendor": "N-able",
  "product": "N-central",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 26.4.1"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "26.4.1"
      ],
      "package_name": "N-central",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.6,
  "cvss_src": "other",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N",
  "epss_score": 0.0055,
  "epss_percentile": 0.4648,
  "epss_asof": "2026-11-17",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 12.395049466666666,
  "t0_at": "2026-11-10T21:25:23.173000+00:00",
  "signals": {
    "kev": {
      "at": "2026-11-17T00:00:00+00:00",
      "days": 7,
      "is_lower_bound": false,
      "measured_at": "2026-11-10T21:25:23.173000+00:00",
      "precision": "day",
      "url": "https://vulncheck.com/cve/CVE-2026-125882"
    },
    "trigger_signal": {
      "at": "2026-11-17T00:00:00+00:00",
      "days": 6.10737068287037,
      "is_lower_bound": false,
      "measured_at": "2026-11-10T21:25:23.173000+00:00",
      "url": "https://vulncheck.com/cve/CVE-2026-125882"
    }
  }
}

published 2026-11-17 18:44Z
last change 2026-11-18 21:43Z

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.