SECURITY_THREAT_PULSE
LIVE
LAST UPDATED
FIRST SEEN
4 SOURCES ON THIS EVENT
◆ WATCHCVE-2026-2699 · CVSS 9.8

Progress ShareFile Storage Zones Controller: attackers can run their own code

AFFECTSProgress ShareFile Storage Zones Controller

OFFICIAL NAME: EAR vulnerability in Progress ShareFile Storage Zones Controller (SZC)

WHAT IT IS · FILE TRANSFERIt holds files you swap with customers and partners, a common target for bulk data theft.

DO THIS FIRSTPatch it today and check it for files or accounts you do not recognize. Not sure if you use it? Send this page to your IT provider or security lead and ask.

TECHNICAL SUMMARY Customer Managed ShareFile Storage Zones Controller (SZC) allows an unauthenticated attacker to access restricted configuration pages. This leads to changing system configuration and potential remote code execution.

WHY THIS VERDICT Attack attempts are confirmed, with no confirmed exploitation yet.

WHY IT RANKS HERE The product faces the internet or gives remote access. Ready-made attack tools are public. The first report is 20 days old.

HIGHEST CONFIRMED RUNG
TRIED
CISA KEV
NOT YET
EXPLOIT CODE
READY TO USE
// EVIDENCE LADDER

How far has it climbed?

CONFIRMED
REPORTED
NO EVIDENCE

  1. 01 TALK

    □ NO EVIDENCE YET
    NEWEST EVIDENCE NONE YET

    No evidence yet.

    SRC: NONE YET

  2. 02 EXPOSED

    □ NOT TRACKED YET
    NO SOURCE FOR THIS STEP YET

    We have no source that counts exposed systems yet. Internet scan data needs a partnership we do not have. No evidence here does not mean nothing is exposed.

  3. 03 TRIED

    ■ CONFIRMED
    NEWEST EVIDENCE · 1 SOURCE

    Attack attempts on CVE-2026-2699 seen by honeypots (Shadowserver via CIRCL). Attack attempts on CVE-2026-2699 seen by honeypots (Shadowserver via CIRCL).

  4. 04 EXPLOITED

    □ NO EVIDENCE YET
    NEWEST EVIDENCE NONE YET

    No evidence yet.

    SRC: NONE YET

  5. 05 DAMAGE

    □ NOT TRACKED YET
    NO SOURCE FOR THIS STEP YET

    Breach notices and filings rarely name the flaw that was used, so we cannot link them to this event yet. No evidence here does not mean no harm.

// THE CLOCK

When each thing happened

  1. DISCLOSED
    CVE-2026-2699 published
  2. EXPLOIT CODE PUBLIC
    DATE UNKNOWN
  3. FIRST ATTACK REPORT
    CIRCL Vulnerability-Lookup sightings
  4. CISA KEV LISTING
    NOT YET
  5. US FEDERAL DEADLINE
    NOT YET
Attacks were reported 203 days after disclosure.
// ASK YOUR TEAM

Questions to ask this week

// TIMELINE · PACIFIC TIME

How it unfolded

  1. MAR 25, 2026
    2 public GitHub repositories claim a proof of concept for CVE-2026-2699
  2. APR 2, 2026
    CISA Vulnrichment notes a public proof of concept for CVE-2026-2699
  3. Attack activity. OCT 21, 2026
    Attack attempts on CVE-2026-2699 seen by honeypots (Shadowserver via CIRCL) (2 reports, latest OCT 22)

SOURCES

  1. [1] nuclei-templates: Nuclei scan template: Progress ShareFile Storage Zones Controller - Authentication Bypass, OCT 24
  2. [2] CIRCL Vulnerability-Lookup sightings: Attack attempts on CVE-2026-2699 seen by honeypots (Shadowserver via CIRCL), OCT 22
  3. [3] CVE List V5 and CISA Vulnrichment: CISA Vulnrichment notes a public proof of concept for CVE-2026-2699, APR 2
  4. [4] PoC-in-GitHub: 2 public GitHub repositories claim a proof of concept for CVE-2026-2699, MAR 25