CVE-2026-84295

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

GHSA-qwpp-fggf-7h3c ↗EUVD-2026-113016 ↗

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.
Progress Software WS_FTP Server < 2024.0.6; < 2025.0.3
fixed in 2024.0.6, 2025.0.3
CWE-287 Improper Authentication
ETK-2026-2983Zero's internal tracking ID, independent of the CVE number., permanent identifier
2h 40msince last run
22mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h46m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Progress Software WS_FTP Server on Windows before 2024.0.6 and 2025.0.3 is affected by an improper authentication flaw. An unauthenticated remote attacker could access sensitive information, including administrative credentials, when able to reach the affected server.

mitigation

Upgrade WS_FTP Server to 2024.0.6 or 2025.0.3, as applicable. Restrict network access to the server until the update is deployed.

fixed in 2024.0.6, 2025.0.3

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-2983",
  "cve_id": "CVE-2026-84295",
  "display_id": "CVE-2026-84295",
  "ghsa_id": "GHSA-qwpp-fggf-7h3c",
  "euvd_id": "EUVD-2026-113016",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper authentication in WS_FTP Server",
  "summary": "Progress Software WS_FTP Server on Windows before 2024.0.6 and 2025.0.3 is affected by an improper authentication flaw. An unauthenticated remote attacker could access sensitive information, including administrative credentials, when able to reach the affected server.",
  "mitigation": "Upgrade WS_FTP Server to 2024.0.6 or 2025.0.3, as applicable. Restrict network access to the server until the update is deployed.",
  "vendor": "Progress Software",
  "product": "WS_FTP Server",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 2024.0.6",
        ">= 0, < 2025.0.3"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2024.0.6",
        "2025.0.3"
      ],
      "package_name": "WS_FTP Server",
      "purl": null
    }
  ],
  "cwes": [
    287
  ],
  "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": 21.51478825,
  "t0_at": "2026-10-29T15:45:08.601000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-29T15:45:08.601000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-29T15:45:08.601000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-84295"
    }
  }
}

published 2026-10-29 16:09Z
last change 2026-10-29 18:58Z

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.