Skip to content
major vulnerability· requires attention

Affects widely used enterprise MFT (Progress MOVEit); auth bypass can enable large-scale data theft and operational disruption similar to past MOVEit incidents.

Applications

CVE-2026-89067

8.8
High
EPSS 0.56%Patch availableOct 17, 2026

Authentication bypass in Progress MOVEit Transfer enabling unauthorized access.

common questions

Is CVE-2026-89067 being exploited?

Not confirmed. CVE-2026-89067 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.56% probability of exploitation in the next 30 days.

How severe is CVE-2026-89067?

CVE-2026-89067 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-89067?

Yes. A fix has been recorded for CVE-2026-89067. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-89067 affect?

CVE-2026-89067 affects Progress MOVEit Transfer <2025.1.6, Progress MOVEit Transfer 2026.0.0 - 2026.0.3. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-89067?

Upgrade to 2025.1.6 or 2026.0.4; restrict access, rotate credentials, and audit logs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Progress MOVEit Transfer <2025.1.6Progress MOVEit Transfer 2026.0.0 - 2026.0.3
impact

Authentication bypass allows attackers to access MOVEit accounts/files, exfiltrate data, and perform unauthorized actions.

action required

Immediate action required

affected versions
Progress MOVEit Transfer
  • affected< 2025.1.6
  • affected>= 2026.0.0 and < 2026.0.4

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free