CVE-2026-82819

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

GHSA-jxgv-cgf3-xqr5 ↗EUVD-2026-107041 ↗

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.
Cerberus FTP Server < 2026.3.0
fixed in 2026.3.0
CWE-40 Path Traversal: 'UNCsharename' (Windows UNC Share)
ETK-2026-2288Zero's internal tracking ID, independent of the CVE number., permanent identifier
29msince last run
10mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+4h37m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Cerberus FTP Server installations that have not been updated to 2026.3.0 are affected by UNC path injection. An authenticated remote user can induce SMB authentication from the server and obtain the service account's Net-NTLMv2 hash; access to a valid account is required.

mitigation

Upgrade Cerberus FTP Server to version 2026.3.0. Restrict untrusted authenticated users until the update is deployed.

fixed in 2026.3.0

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
10m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-21 04:30Z
Δ 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-21 04:30Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2288",
  "cve_id": "CVE-2026-82819",
  "display_id": "CVE-2026-82819",
  "ghsa_id": "GHSA-jxgv-cgf3-xqr5",
  "euvd_id": "EUVD-2026-107041",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authenticated UNC path injection in Cerberus FTP Server",
  "summary": "Cerberus FTP Server installations that have not been updated to 2026.3.0 are affected by UNC path injection. An authenticated remote user can induce SMB authentication from the server and obtain the service account's Net-NTLMv2 hash; access to a valid account is required.",
  "mitigation": "Upgrade Cerberus FTP Server to version 2026.3.0. Restrict untrusted authenticated users until the update is deployed.",
  "vendor": "Cerberus",
  "product": "Cerberus FTP Server",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 2026.3.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2026.3.0"
      ],
      "package_name": "Cerberus FTP Server",
      "purl": null
    }
  ],
  "cwes": [
    40
  ],
  "cvss_score": 7.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 10.3880716,
  "t0_at": "2026-10-21T04:30:40.808000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-21T04:30:40.808000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-21T04:30:40.808000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-82819"
    }
  }
}

published 2026-10-21 05:17Z
last change 2026-10-21 09:20Z

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.