CVE-2026-122013

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

GHSA-jm4m-752p-2g2x ↗EUVD-2026-117099 ↗

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.
Comfast CF-WR632AX 2.6.0.1
ETK-2026-3552Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 18msince last run
9mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+2h40m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Comfast CF-WR632AX version 2.6.0.1 is affected by a path-traversal issue in its web-management multipart upload handling. A remote attacker may cause unintended filesystem path access by supplying a crafted upload filename, provided they can reach the device's management service.

mitigation

Restrict the device management interface to trusted administrative networks and block untrusted remote access. Monitor for a vendor firmware update and apply it when available.

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-3552",
  "cve_id": "CVE-2026-122013",
  "display_id": "CVE-2026-122013",
  "ghsa_id": "GHSA-jm4m-752p-2g2x",
  "euvd_id": "EUVD-2026-117099",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Path traversal in Comfast CF-WR632AX multipart parser",
  "summary": "Comfast CF-WR632AX version 2.6.0.1 is affected by a path-traversal issue in its web-management multipart upload handling. A remote attacker may cause unintended filesystem path access by supplying a crafted upload filename, provided they can reach the device's management service.",
  "mitigation": "Restrict the device management interface to trusted administrative networks and block untrusted remote access. Monitor for a vendor firmware update and apply it when available.",
  "vendor": "Comfast",
  "product": "CF-WR632AX",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "2.6.0.1"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "CF-WR632AX",
      "purl": null
    }
  ],
  "cwes": null,
  "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": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 9.315794983333333,
  "t0_at": "2026-11-04T20:45:20.840000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-04T20:45:20.840000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-04T20:45:20.840000+00:00",
      "url": "https://github.com/advisories/GHSA-jm4m-752p-2g2x"
    }
  }
}

published 2026-11-04 23:16Z
last change 2026-11-05 00:05Z

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.