CVE-2026-105219

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

GHSA-fp33-4hh4-xjj5 ↗EUVD-2026-92122 ↗

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.
mwilliamson mammoth.js >= 1.3.0, < 1.12.3
fixed in 1.12.3
CWE-1333 Inefficient Regular Expression Complexity
ETK-2026-574, permanent identifier
16d 20h 10msince last run
30mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+2h17m
0
+4h
+6h
+8h
+10h
+12h

description

mammoth.js versions 1.3.0 through 1.12.2 are affected by a regular expression denial-of-service issue in style-map parsing. An attacker who can provide a crafted DOCX document for processing may cause the Node.js event loop to become blocked. Exploitation requires the application to process the attacker-controlled document with the affected component.

mitigation

Upgrade mammoth.js to version 1.12.3 or later. Until upgrading, restrict processing of untrusted DOCX files to reduce exposure.

fixed in 1.12.3

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.36%28th percentile
agent run time
30m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-04 17:09Z
Δ 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-04 17:09Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-574",
  "cve_id": "CVE-2026-105219",
  "display_id": "CVE-2026-105219",
  "ghsa_id": "GHSA-fp33-4hh4-xjj5",
  "euvd_id": "EUVD-2026-92122",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Regular expression denial of service in mammoth.js",
  "summary": "mammoth.js versions 1.3.0 through 1.12.2 are affected by a regular expression denial-of-service issue in style-map parsing. An attacker who can provide a crafted DOCX document for processing may cause the Node.js event loop to become blocked. Exploitation requires the application to process the attacker-controlled document with the affected component.",
  "mitigation": "Upgrade mammoth.js to version 1.12.3 or later. Until upgrading, restrict processing of untrusted DOCX files to reduce exposure.",
  "vendor": "mwilliamson",
  "product": "mammoth.js",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.3.0, < 1.12.3"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.12.3"
      ],
      "package_name": "mammoth.js",
      "purl": null
    }
  ],
  "cwes": [
    1333
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.0036,
  "epss_percentile": 0.2808,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 29.555955383333334,
  "t0_at": "2026-10-04T17:09:54.186000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-04T17:09:54.186000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-04T17:09:54.186000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-105219"
    }
  }
}

published 2026-10-04 17:30Z
last change 2026-10-21 07:48Z

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.