CVE-2026-39759

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

GHSA-pwx7-8gm2-cp29 ↗EUVD-2026-93268 ↗

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.
AmentoTech Workreap Core >= n/a, <= 3.4.5
CWE-434 Unrestricted Upload of File with Dangerous Type
ETK-2026-750, permanent identifier
13d 01h 41msince last run
19mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+51h02m
0
+2h
+4h
+6h
+8h
+10h

description

Workreap Core versions through 3.4.5 are affected by an arbitrary file-upload vulnerability. An attacker able to use the relevant employer or sales-representative functionality may upload files outside intended restrictions.

mitigation

Restrict employer and sales-representative access to trusted users, and disable or limit the affected upload functionality where operationally possible. Monitor uploaded content and apply a vendor-provided update 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.48%40th percentile
agent run time
19m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-06 08:34Z
Δ 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-06 08:34Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-750",
  "cve_id": "CVE-2026-39759",
  "display_id": "CVE-2026-39759",
  "ghsa_id": "GHSA-pwx7-8gm2-cp29",
  "euvd_id": "EUVD-2026-93268",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Arbitrary file upload in Workreap Core",
  "summary": "Workreap Core versions through 3.4.5 are affected by an arbitrary file-upload vulnerability. An attacker able to use the relevant employer or sales-representative functionality may upload files outside intended restrictions.",
  "mitigation": "Restrict employer and sales-representative access to trusted users, and disable or limit the affected upload functionality where operationally possible. Monitor uploaded content and apply a vendor-provided update when one is available.",
  "vendor": "AmentoTech",
  "product": "Workreap Core",
  "affected": [
    {
      "affected_notes": [
        ">= n/a, <= 3.4.5"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "workreap_core",
      "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.0048,
  "epss_percentile": 0.4007,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 19.364025116666667,
  "t0_at": "2026-10-06T08:34:26.777000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-06T08:34:26.777000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-06T08:34:26.777000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-39759"
    }
  }
}

published 2026-10-06 09:25Z
last change 2026-10-21 12: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.