Cyber Resilience

CVE-2026-0972

Fortra Goanywhere Managed File Transfer ≤ 7.10.0

Published
21 April 2026
Modified
23 April 2026
Patch / advisory
View advisory
CVSS Score v3.1 5.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
EPSS Score 0.0015 5th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-0972 is a medium-severity Injection (CWE-74) vulnerability in Fortra Goanywhere Managed File Transfer. Its CVSS base score is 5.4 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 5th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SI-15 (Information Output Filtering) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

HTML injection is possible in system generated emails in Fortra's GoAnywhere MFT prior to 7.10.0. Note: The title, details, and description of this CVE were corrected post-publishing.

CWE(s)
CWE-74

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
attack.mitre.org →
Why these techniques?

HTML injection in system emails directly enables content injection (T1659).

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-1089Same product: Fortra Goanywhere Managed File Transfer
CVE-2026-41237Shared CWE-74
CVE-2026-10729Shared CWE-74
CVE-2026-0865Shared CWE-74
CVE-2025-9797Shared CWE-74
CVE-2024-10491Shared CWE-74
CVE-2025-67746Shared CWE-74
CVE-2026-35515Shared CWE-74
CVE-2026-47644Shared CWE-74
CVE-2026-1154Shared CWE-74

Affected Assets

fortra
goanywhere managed file transfer
≤ 7.10.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-15 Information Output Filtering
  • SI-10 Information Input Validation
Detect
Catch it (NIST detect / respond)
  • SI-7 Software, Firmware, and Information Integrity
Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.2.1
  • V1.2.3
  • V1.2.5
  • V1.2.8

Mitigating Controls (NIST 800-53 r5) AI

SI-15 Information Output Filtering good match
prevent

Directly requires filtering/sanitization of information (HTML) in system-generated outputs such as emails before transmission, preventing the injection described in CWE-74.

SI-10 Information Input Validation good match
prevent

Requires validation and neutralization of inputs used to construct emails, blocking the special-element injection that enables HTML content in GoAnywhere MFT.

SI-7 Software, Firmware, and Information Integrity partial match
detect

Provides integrity verification of generated email content, allowing detection of unauthorized HTML modifications introduced by the flaw.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and output encoding that prevent injection flaws.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing in development catches injection vulnerabilities before release.

A.8.15 Logging partial match
detects

Logging supports detection of injection attempts but does not prevent the weakness.

A.8.16 Monitoring activities partial match
detects

Monitoring activities can identify active injection attacks after they occur.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and output encoding that directly prevent injection flaws.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for controls against injection attacks in software design.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce injection surfaces but do not prescribe specific neutralization techniques.

References