CVE-2026-62320

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

GHSA-5gqf-6pmp-7932 ↗EUVD-2026-131690 ↗

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.
Netatalk 1.5.0-4.5.0
CWE-20 Improper Input Validation
ETK-2026-5072Zero's internal tracking ID, independent of the CVE number., permanent identifier
3h 04msince last run
43mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h18m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Netatalk versions 1.5.0 through versions before 4.5.1 mishandle oversized DSI frame lengths on the AFP DSI service. A remote unauthenticated attacker able to reach TCP port 548 can cause queued data to be interpreted as additional attacker-controlled DSI frames on the same connection.

mitigation

Upgrade Netatalk to version 4.5.1 or later. Until upgraded, restrict access to the AFP DSI service on TCP port 548 to trusted networks.

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.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
43m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-20 17:27Z
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-11-20 17:27Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-5072",
  "cve_id": "CVE-2026-62320",
  "display_id": "CVE-2026-62320",
  "ghsa_id": "GHSA-5gqf-6pmp-7932",
  "euvd_id": "EUVD-2026-131690",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated DSI frame smuggling in Netatalk",
  "summary": "Netatalk versions 1.5.0 through versions before 4.5.1 mishandle oversized DSI frame lengths on the AFP DSI service. A remote unauthenticated attacker able to reach TCP port 548 can cause queued data to be interpreted as additional attacker-controlled DSI frames on the same connection.",
  "mitigation": "Upgrade Netatalk to version 4.5.1 or later. Until upgraded, restrict access to the AFP DSI service on TCP port 548 to trusted networks.",
  "vendor": "Netatalk",
  "product": "netatalk",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "1.5.0-4.5.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Netatalk",
      "purl": null
    }
  ],
  "cwes": [
    20
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 42.61593843333333,
  "t0_at": "2026-11-20T17:27:11.873000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-20T17:27:11.873000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-20T17:27:11.873000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-62320"
    }
  }
}

published 2026-11-20 18:02Z
last change 2026-11-20 21:26Z

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.