CVE-2026-118035

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

GHSA-pmr9-x859-mh5c ↗EUVD-2026-112037 ↗

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.
Progress Software Telerik Document Processing Libraries < 2026.3.1027
fixed in 2026.3.1027
CWE-674 Uncontrolled Recursion
ETK-2026-2866Zero's internal tracking ID, independent of the CVE number., permanent identifier
3h 19msince last run
18mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h45m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Telerik Document Processing Libraries before 2026.3.1027 are affected in the RadWordsProcessing component. An unauthenticated attacker who can supply a DOCX, DOC, RTF, or HTML document may cause the host process to hang or terminate.

mitigation

Upgrade Telerik Document Processing Libraries to version 2026.3.1027 or later. Until upgraded, restrict untrusted document inputs to affected processing workflows.

fixed in 2026.3.1027

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
18m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-28 12:31Z
Δ 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-10-28 12:31Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2866",
  "cve_id": "CVE-2026-118035",
  "display_id": "CVE-2026-118035",
  "ghsa_id": "GHSA-pmr9-x859-mh5c",
  "euvd_id": "EUVD-2026-112037",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Resource exhaustion in Telerik RadWordsProcessing",
  "summary": "Telerik Document Processing Libraries before 2026.3.1027 are affected in the RadWordsProcessing component. An unauthenticated attacker who can supply a DOCX, DOC, RTF, or HTML document may cause the host process to hang or terminate.",
  "mitigation": "Upgrade Telerik Document Processing Libraries to version 2026.3.1027 or later. Until upgraded, restrict untrusted document inputs to affected processing workflows.",
  "vendor": "Progress Software",
  "product": "Telerik Document Processing Libraries",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 2026.3.1027"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2026.3.1027"
      ],
      "package_name": "Telerik Document Processing Libraries",
      "purl": null
    }
  ],
  "cwes": [
    674
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 18.129501183333332,
  "t0_at": "2026-10-28T12:31:56.249000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-28T12:31:56.249000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-28T12:31:56.249000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-118035"
    }
  }
}

published 2026-10-28 12:58Z
last change 2026-10-28 16:08Z

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.