CVE-2026-62024

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

GHSA-hpfr-835p-qqmv ↗EUVD-2026-96462 ↗

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.
CodeBard Help Desk >= n/a, <= 1.1.2
CWE-434 Unrestricted Upload of File with Dangerous Type
ETK-2026-1187Zero's internal tracking ID, independent of the CVE number., permanent identifier
10d 05h 52msince last run
38mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+3h19m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

CodeBard Help Desk versions through 1.1.2 are affected by an arbitrary file upload flaw. A subscriber may be able to upload files outside intended restrictions; exploiting the issue requires subscriber-level access.

mitigation

Restrict subscriber accounts and disable or tightly limit file-upload functionality where possible. Monitor upload locations for unexpected files and apply a vendor-provided fixed release when one is available.

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.45%37th percentile
agent run time
38m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-10 19:35Z
Δ 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-10 19:35Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1187",
  "cve_id": "CVE-2026-62024",
  "display_id": "CVE-2026-62024",
  "ghsa_id": "GHSA-hpfr-835p-qqmv",
  "euvd_id": "EUVD-2026-96462",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Subscriber arbitrary file upload in CodeBard Help Desk",
  "summary": "CodeBard Help Desk versions through 1.1.2 are affected by an arbitrary file upload flaw. A subscriber may be able to upload files outside intended restrictions; exploiting the issue requires subscriber-level access.",
  "mitigation": "Restrict subscriber accounts and disable or tightly limit file-upload functionality where possible. Monitor upload locations for unexpected files and apply a vendor-provided fixed release when one is available.",
  "vendor": "CodeBard",
  "product": "CodeBard Help Desk",
  "affected": [
    {
      "affected_notes": [
        ">= n/a, <= 1.1.2"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "codebard-help-desk",
      "purl": null
    }
  ],
  "cwes": [
    434
  ],
  "cvss_score": 9.9,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
  "epss_score": 0.0045,
  "epss_percentile": 0.3753,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 38.282903033333334,
  "t0_at": "2026-10-10T19:35:28.051000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-10T19:35:28.051000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-10T19:35:28.051000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-62024"
    }
  }
}

published 2026-10-10 20:20Z
last change 2026-10-21 04: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.