CVE-2026-61738

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

GHSA-q3g8-3cf7-744f ↗EUVD-2026-114001 ↗

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.
socfortress CoPilot < latest
fixed in latest
CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
ETK-2026-3088Zero's internal tracking ID, independent of the CVE number., permanent identifier
2h 48msince last run
29mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h25m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

socfortress CoPilot versions before 0.1.77 mishandle upload filenames in the ScoutSuite GCP report endpoint. An authenticated administrator or analyst can write accepted JSON content outside the intended report directory, potentially overwriting files and disrupting the application.

mitigation

Upgrade CoPilot to version 0.1.77 or later. Until upgraded, restrict administrator and analyst access to the affected GCP report upload function.

fixed in latest

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
29m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-30 14:36Z
Δ 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-30 14:36Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3088",
  "cve_id": "CVE-2026-61738",
  "display_id": "CVE-2026-61738",
  "ghsa_id": "GHSA-q3g8-3cf7-744f",
  "euvd_id": "EUVD-2026-114001",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Path traversal file write in socfortress CoPilot",
  "summary": "socfortress CoPilot versions before 0.1.77 mishandle upload filenames in the ScoutSuite GCP report endpoint. An authenticated administrator or analyst can write accepted JSON content outside the intended report directory, potentially overwriting files and disrupting the application.",
  "mitigation": "Upgrade CoPilot to version 0.1.77 or later. Until upgraded, restrict administrator and analyst access to the affected GCP report upload function.",
  "vendor": "socfortress",
  "product": "CoPilot",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< latest"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "latest"
      ],
      "package_name": "socfortress/CoPilot",
      "purl": null
    }
  ],
  "cwes": [
    22
  ],
  "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": 29.330419533333334,
  "t0_at": "2026-10-30T14:36:10.445000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-30T14:36:10.445000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-30T14:36:10.445000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-61738"
    }
  }
}

published 2026-10-30 15:32Z
last change 2026-10-30 17:12Z

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.