CVE-2026-51568

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

GHSA-wfpw-mwxx-8vrf ↗EUVD-2026-90428 ↗

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.
Agentscope n/a
ETK-2026-167, permanent identifier
20d 09h 34msince last run
28mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+23h49m
0
+2h
+4h
+6h
+8h
+10h

description

Agentscope versions 1.0.0 through 1.0.18 are affected by path traversal in write_text_file. An attacker may be able to cause file writes outside the intended directory if they can influence paths passed to this functionality. The advisory does not state a fixed version or further preconditions.

mitigation

Restrict access to functionality that can invoke write_text_file and validate or constrain file paths to an approved directory. Until a vendor update is identified, run the affected component with least-privilege filesystem permissions.

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.
0.32%23rd percentile
agent run time
28m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-30 00:00Z
Δ 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: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-09-30 00:00Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-167",
  "cve_id": "CVE-2026-51568",
  "display_id": "CVE-2026-51568",
  "ghsa_id": "GHSA-wfpw-mwxx-8vrf",
  "euvd_id": "EUVD-2026-90428",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Path traversal in Agentscope write_text_file",
  "summary": "Agentscope versions 1.0.0 through 1.0.18 are affected by path traversal in write_text_file. An attacker may be able to cause file writes outside the intended directory if they can influence paths passed to this functionality. The advisory does not state a fixed version or further preconditions.",
  "mitigation": "Restrict access to functionality that can invoke write_text_file and validate or constrain file paths to an approved directory. Until a vendor update is identified, run the affected component with least-privilege filesystem permissions.",
  "vendor": null,
  "product": "Agentscope",
  "affected": [
    {
      "affected_notes": [
        "n/a"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "n/a",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AC:L/AV:N/A:N/C:H/I:H/PR:L/S:U/UI:N",
  "epss_score": 0.0032,
  "epss_percentile": 0.2304,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 27.795610116666666,
  "t0_at": "2026-09-30T00:00:00+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-09-30T00:00:00+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-30T00:00:00+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-51568"
    }
  }
}

published 2026-09-30 23:20Z
last change 2026-10-21 08: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.