CVE-2026-39773

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

GHSA-r79f-2598-j89j ↗EUVD-2026-93023 ↗

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 Doctreat Core >= n/a, <= 1.7.0
CWE-266 Incorrect Privilege Assignment
ETK-2026-747, permanent identifier
14d 19h 17msince 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+1h51m
0
+4h
+6h
+8h
+10h
+12h

description

Doctreat Core versions through 1.7.0 are affected by a privilege-escalation vulnerability. An attacker may obtain elevated privileges without authenticating; the advisory does not identify additional preconditions.

mitigation

Restrict access to affected Doctreat Core deployments to trusted networks and users until a vendor correction is available. Monitor vendor advisories and upgrade when a fixed release is published; no fixed version is recorded.

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.
0.29%20th 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

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-10-06 08:34Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-747",
  "cve_id": "CVE-2026-39773",
  "display_id": "CVE-2026-39773",
  "ghsa_id": "GHSA-r79f-2598-j89j",
  "euvd_id": "EUVD-2026-93023",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated privilege escalation in Doctreat Core",
  "summary": "Doctreat Core versions through 1.7.0 are affected by a privilege-escalation vulnerability. An attacker may obtain elevated privileges without authenticating; the advisory does not identify additional preconditions.",
  "mitigation": "Restrict access to affected Doctreat Core deployments to trusted networks and users until a vendor correction is available. Monitor vendor advisories and upgrade when a fixed release is published; no fixed version is recorded.",
  "vendor": "AmentoTech",
  "product": "Doctreat Core",
  "affected": [
    {
      "affected_notes": [
        ">= n/a, <= 1.7.0"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "doctreat_core",
      "purl": null
    }
  ],
  "cwes": [
    266
  ],
  "cvss_score": 10,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H",
  "epss_score": 0.0029,
  "epss_percentile": 0.2007,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 19.02094105,
  "t0_at": "2026-10-06T08:34:35.478000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-06T08:34:35.478000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-06T08:34:35.478000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-39773"
    }
  }
}

published 2026-10-06 09:05Z
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.