CVE-2026-53882

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

GHSA-gvx8-w6x3-5c2c ↗EUVD-2026-101982 ↗

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.
QNAP Systems Inc. Virtualization Station >= 4.1.x, < 4.1.1.130
fixed in 4.1.1.130
ETK-2026-1684Zero's internal tracking ID, independent of the CVE number., permanent identifier
4d 03h 48msince last run
36mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+55h33m
0
+2h
+4h
+6h
+8h
+10h

description

QNAP Virtualization Station before 4.1.1.130 is affected by an improper link-resolution issue during file access. An attacker with a user account may exploit the flaw to compromise system security.

mitigation

Upgrade Virtualization Station to version 4.1.1.130 or later. Restrict and review user-account access until the update is installed.

fixed in 4.1.1.130

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.47%39th percentile
agent run time
36m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-15 09:31Z
Δ 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-15 09:31Z
    ghsa: trigger signal, started the run
  2. 2026-10-15 09:31Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1684",
  "cve_id": "CVE-2026-53882",
  "display_id": "CVE-2026-53882",
  "ghsa_id": "GHSA-gvx8-w6x3-5c2c",
  "euvd_id": "EUVD-2026-101982",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Link-following vulnerability in Virtualization Station",
  "summary": "QNAP Virtualization Station before 4.1.1.130 is affected by an improper link-resolution issue during file access. An attacker with a user account may exploit the flaw to compromise system security.",
  "mitigation": "Upgrade Virtualization Station to version 4.1.1.130 or later. Restrict and review user-account access until the update is installed.",
  "vendor": "QNAP Systems Inc.",
  "product": "Virtualization Station",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 4.1.x, < 4.1.1.130"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "4.1.1.130"
      ],
      "package_name": "Virtualization Station",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
  "epss_score": 0.0047,
  "epss_percentile": 0.3915,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 36.01704156666667,
  "t0_at": "2026-10-15T09:31:51.390000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-15T09:31:51.390000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-15T09:31:51.390000+00:00",
      "url": "https://github.com/advisories/GHSA-gvx8-w6x3-5c2c"
    }
  }
}

published 2026-10-15 14:38Z
last change 2026-10-21 05:31Z

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.