CVE-2026-62331

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

GHSA-48v2-6jcm-fc99 ↗EUVD-2026-114361 ↗

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.
go:github.com/mtzanidakis/praktor <= 0.9.0
fixed in 0.9.1
ETK-2026-3387Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:golang/github.com/mtzanidakis/praktor
1h 34msince last run
26mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+95h27m
0
+2h
+4h
+6h
+8h
+10h

description

praktor versions through 0.9.0 allow Telegram upload filenames to write outside the intended uploads directory within the persistent agent workspace. A sender who can message the bot may plant or overwrite files later read by the agent, particularly when the default empty telegram.allow_from setting permits all senders.

mitigation

Upgrade github.com/mtzanidakis/praktor to version 0.9.1. Until upgraded, restrict telegram.allow_from to trusted Telegram user IDs.

fixed in 0.9.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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
26m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-30 19:00Z
Δ 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-10-30 19:00Z
    ghsa: trigger signal, started the run
  2. 2026-10-30 19:00Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3387",
  "cve_id": "CVE-2026-62331",
  "display_id": "CVE-2026-62331",
  "ghsa_id": "GHSA-48v2-6jcm-fc99",
  "euvd_id": "EUVD-2026-114361",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Path traversal in praktor Telegram uploads",
  "summary": "praktor versions through 0.9.0 allow Telegram upload filenames to write outside the intended uploads directory within the persistent agent workspace. A sender who can message the bot may plant or overwrite files later read by the agent, particularly when the default empty `telegram.allow_from` setting permits all senders.",
  "mitigation": "Upgrade github.com/mtzanidakis/praktor to version 0.9.1. Until upgraded, restrict `telegram.allow_from` to trusted Telegram user IDs.",
  "vendor": "go",
  "product": "go:github.com/mtzanidakis/praktor",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 0.9.0"
      ],
      "ecosystem": "go",
      "fixed_versions": [
        "0.9.1"
      ],
      "package_name": "github.com/mtzanidakis/praktor",
      "purl": "pkg:golang/github.com/mtzanidakis/praktor"
    }
  ],
  "cwes": null,
  "cvss_score": 8.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 26.185007416666668,
  "t0_at": "2026-10-30T19:00:25.777000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-30T19:00:25.777000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-30T19:00:25.777000+00:00",
      "url": "https://github.com/advisories/GHSA-48v2-6jcm-fc99"
    }
  }
}

published 2026-11-03 18:00Z
last change 2026-11-03 18:45Z

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.