ETK-2026-3617Zero's internal tracking ID, independent of the CVE number.

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

GHSA-3fwm-h59w-j268 ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
hedgedoc <= 1.12.0
fixed in 1.12.1
ETK-2026-3617Zero's internal tracking ID, independent of the CVE number., no cve assigned
11h 43msince last run
14mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
trigger signal −17h02mwaiting for further signals−11h43m
−6h
0

description

HedgeDoc through 1.12.0 has prototype pollution in authenticated note-history update handling. An authenticated user can cause server errors and crash the Node.js process. Deployments that use signed-in accounts and permit history changes are affected.

mitigation

Upgrade HedgeDoc to version 1.12.1 or later. If an immediate upgrade is not possible, use a reverse proxy to restrict the authenticated note-history modification endpoint, understanding that this disables history changes for signed-in users.

fixed in 1.12.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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
14m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ 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-11-04 21:38Z

this entry in the feed

GET /api/v1/feed/ETK-2026-3617

{
  "etk_id": "ETK-2026-3617",
  "cve_id": null,
  "display_id": "ETK-2026-3617",
  "ghsa_id": "GHSA-3fwm-h59w-j268",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Prototype pollution in HedgeDoc note-history updates",
  "summary": "HedgeDoc through 1.12.0 has prototype pollution in authenticated note-history update handling. An authenticated user can cause server errors and crash the Node.js process. Deployments that use signed-in accounts and permit history changes are affected.",
  "mitigation": "Upgrade HedgeDoc to version 1.12.1 or later. If an immediate upgrade is not possible, use a reverse proxy to restrict the authenticated note-history modification endpoint, understanding that this disables history changes for signed-in users.",
  "vendor": null,
  "product": "hedgedoc",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 1.12.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.12.1"
      ],
      "package_name": "hedgedoc",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 13.642998683333333,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-11-04T21:38:20+00:00",
      "days": -0.7094376611689814,
      "is_lower_bound": true,
      "measured_at": "2026-11-05T14:39:55.479817+00:00",
      "url": "https://github.com/hedgedoc/hedgedoc/security/advisories/GHSA-3fwm-h59w-j268"
    }
  }
}

published 2026-11-05 10:54Z
last change 2026-11-05 14:29Z

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.