CVE-2026-133835

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

GHSA-pg82-9j2w-8982 ↗EUVD-2026-131879 ↗

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.
hankcs HanLP 2.1.0; 2.1.1; 2.1.2; 2.1.3; 2.1.4; 2.1.5; 2.1.6
ETK-2026-5101Zero's internal tracking ID, independent of the CVE number., permanent identifier
8h 06msince last run
11mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+3h44m
0
+2h
+6h
+8h
+10h
+12h

description

HanLP versions through 2.1.6 can write archive contents outside the intended extraction directory when handling TAR files. An attacker may alter files accessible to the extraction process if they can cause it to process a crafted archive.

mitigation

Upgrade HanLP to version 2.1.7 or later. Until upgraded, do not extract untrusted TAR archives with the affected HanLP workflow.

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
11m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-20 21:15Z
Δ 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-20 21:15Z
    ghsa: trigger signal, started the run
  2. 2026-11-20 21:15Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-5101",
  "cve_id": "CVE-2026-133835",
  "display_id": "CVE-2026-133835",
  "ghsa_id": "GHSA-pg82-9j2w-8982",
  "euvd_id": "EUVD-2026-131879",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Path traversal in HanLP TAR archive extraction",
  "summary": "HanLP versions through 2.1.6 can write archive contents outside the intended extraction directory when handling TAR files. An attacker may alter files accessible to the extraction process if they can cause it to process a crafted archive.",
  "mitigation": "Upgrade HanLP to version 2.1.7 or later. Until upgraded, do not extract untrusted TAR archives with the affected HanLP workflow.",
  "vendor": "hankcs",
  "product": "HanLP",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "2.1.0",
        "2.1.1",
        "2.1.2",
        "2.1.3",
        "2.1.4",
        "2.1.5",
        "2.1.6"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "HanLP",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 10.603910816666668,
  "t0_at": "2026-11-20T21:15:11.321000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-20T21:15:11.321000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-20T21:15:11.321000+00:00",
      "url": "https://github.com/advisories/GHSA-pg82-9j2w-8982"
    }
  }
}

published 2026-11-21 00:48Z
last change 2026-11-21 08:35Z

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.