CVE-2026-112343

validatingZero is analyzing and reversing it now.

EUVD-2026-109966 ↗

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.
Syncplify, Inc. Syncplify Server! < 8.8.0
fixed in 8.8.0
CWE-41 Improper Resolution of Path Equivalence
ETK-2026-2665Zero's internal tracking ID, independent of the CVE number., permanent identifier
48mrunning
patch analysiscurrent stage
timeline
0 = trigger signal
trigger signal (cve.org) +0hvalidating
0
+1h
+2h
+3h
+4h
+5h

description

Syncplify Server! versions before 8.8.0 can fail to enforce configured per-path permission overrides. An authenticated SFTP user may access protected directories for uploads or downloads by using alternate path representations. The issue applies where per-path restrictions are relied upon on a case-insensitive filesystem.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Upgrade Syncplify Server! to version 8.8.0 or later. Until upgraded, restrict SFTP access for accounts that could reach protected paths and review per-path permission configurations.

fixed in 8.8.0

check
building now
exploit
not yet
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.
–
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.
–
agent run time
48m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-26 15:54Z
Δ 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

Run in progress: no artifact yet.

source signals

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

  1. 2026-10-26 15:54Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2665",
  "cve_id": "CVE-2026-112343",
  "display_id": "CVE-2026-112343",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-109966",
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Per-path permission bypass in Syncplify Server!",
  "summary": "Syncplify Server! versions before 8.8.0 can fail to enforce configured per-path permission overrides. An authenticated SFTP user may access protected directories for uploads or downloads by using alternate path representations. The issue applies where per-path restrictions are relied upon on a case-insensitive filesystem.",
  "mitigation": "Upgrade Syncplify Server! to version 8.8.0 or later. Until upgraded, restrict SFTP access for accounts that could reach protected paths and review per-path permission configurations.",
  "vendor": "Syncplify, Inc.",
  "product": "Syncplify Server!",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 8.8.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "8.8.0"
      ],
      "package_name": "Syncplify Server!",
      "purl": null
    }
  ],
  "cwes": [
    41
  ],
  "cvss_score": 8.6,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 79.77752633333333,
  "t0_at": "2026-10-26T15:54:12.544000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-26T15:54:12.544000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-26T15:54:12.544000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-112343"
    }
  }
}

published 2026-10-26 17:06Z
last change 2026-10-26 19:41Z

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.