What is CVE-2025-10035?

CVE-2025-10035 is Deserialization Vulnerability in GoAnywhere MFT's License Servlet. The supplied enrichment data classifies it as Remote Code Exec mapped to CWE-77 Command Injection; CWE-502 Deserialization of Untrusted Data.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

8 public PoC repositories reported; 2 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, EDR process telemetry, host service logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2025-10035 using CVSS 9.8, EPSS 100%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

Workarounds are not confirmed from current sources. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

Publicly linked actor or ransomware signals in the supplied enrichment data: Bitwise Spider (), Beijing Group (), Lurk (), Silence group (), Pat Bear (), Ransomware use: Known. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVRansomwarecriticalRemote Code Execpublic exploit

CVE-2025-10035

CVE-2025-10035 — Deserialization Vulnerability in GoAnywhere MFT's License Servlet

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2025-10035 in CISA KEV with required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

A deserialization vulnerability in the License Servlet of Fortra's GoAnywhere MFT allows an actor with a validly forged license response signature to deserialize an arbitrary actor-controlled object, possibly leading to command injection.

Published Sep 18, 2025Updated Aug 4, 2026Sources: NVD, Fortra (CNA), CISA, FIRST EPSS, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Sep 29, 2025

EPSS

100%

top of FIRST's scoreset

Affects

Fortra

GoAnywhere MFT

CVSS base

9.8

critical · 2 sources

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade to a patched version (the latest release 7.8.4, or the Sustain Release 7.6.3)

CISA required action

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Federal deadline Oct 20, 2025 — passed 337 days ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Fortra	GoAnywhere MFT	0 to <= 7.8.3	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
10	CVSS 3.1	critical	3.9	6	CNA, Fortra (CNA)
9.8	CVSS 3.1	critical	3.9	5.9	NVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-502 · Deserialization of Untrusted Data

Modify Application Data
Unexpected State
DoS: Resource Consumption (CPU)
Varies by Context

Mitigation: If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.

CWE-77 · Improper Neutralization of Special Elements used in a Command ('Command Injection')

Execute Unauthorized Code or Commands

Mitigation: If at all possible, use library calls rather than external processes to recreate the desired functionality.

Weakness & attack patterns

CWE-77Command Injection
CWE-502Deserialization of Untrusted Data

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-40 · Manipulating Writeable Terminal DevicesCAPEC-75 · Manipulating Writeable Configuration FilesCAPEC-15 · Command DelimitersCAPEC-136 · LDAP InjectionCAPEC-248 · Command InjectionCAPEC-76 · Manipulating Web Input to File System CallsCAPEC-43 · Exploiting Multiple Input Interpretation LayersCAPEC-183 · IMAP/SMTP Command Injection

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Sep 29, 2025

Federal deadline

Oct 20, 2025

passed 337 days ago

Ransomware use

Known

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

2 of the 5 sampled are weaponized

Exploit entries

Exploit-DB and CTI exploit indexes

Malware

Families a CTI source ties to this CVE. One named, with the total it tracks.

Families tracked

Named

Akira

akira, elf.akira, win.akira

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

35 more posts on this CVEShowing 5 of 40 · Who is discussing this CVE, and how loudlyUnlock free

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable GoAnywhere MFT.
Monitor for scanner or exploit-pattern traffic after 8 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPSEDR process telemetryhost service logs

Groups associated with this CVE

Groups reported in connection with this vulnerability. A reported association, not a confirmed observation of that group using it — and not scoped to any sector or campaign.

Bitwise SpiderBeijing GroupLurkSilence groupPat Bear

20 more threat groups on this CVEShowing 5 of 25 · Attribution, campaigns and the malware each one runsUnlock free

ip206.168.190.14348
AlienVault Ransomware-Firehol · Sep 29, 2025
ip45.55.76.21018
AlienVault Ransomware-Firehol · Sep 29, 2025
ip45.56.163.5818
AlienVault Ransomware-Firehol · Sep 29, 2025
ip45.66.249.9348
AlienVault Ransomware-Firehol · Sep 24, 2021
ip62.76.147.10636
AbuseIPDB Hourly Update · Aug 6, 2025

5 more indicators on this CVEShowing 5 of 10 · Hashes, addresses and domains from a live threat exchangeUnlock free

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 9.8 (AV:N)
Aug 4, 2026 · NVD
2025
Added to CISA KEV catalog
Sep 29, 2025 · CISA
Initial · CVE published
Sep 18, 2025 · NVD

Source activity

Readings a source repeats on a schedule, counted rather than listed.

16×SVRS was changedNov 18, 2025 – Aug 11, 2026 · SOCRadar CTI
11×TweetsJan 10, 2026 – Aug 20, 2026 · SOCRadar CTI
1×Github_Repos · Github repository created, sentinel-aidefense/CVE-2025-10035Jul 10, 2026 · SOCRadar CTI
1×CVE modified by MITRE: CVSS metrics updated.Feb 26, 2026 · SOCRadar CTI

References

3 on the record

www.fortra.com/security/advisories/product-security/fi-2025-012
Vendor Advisory, NIST
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-10035
US Government Resource, NIST
nvd.nist.gov/vuln/detail/CVE-2025-10035
Vendor Advisory

Coverage

19 stories from the feeds we poll

14 more reports on this CVEShowing 5 of 19 · Vendor research and security press coverageUnlock free

Elsewhere on this site

Fortraevery CVE for this vendor
September 2025what else CISA listed
Remote Code Execsame class
CWE-77other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

Only the 5 indicator(s) reported for this CVE are available; no packet-level or host-forensic artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2025-10035 is Deserialization Vulnerability in GoAnywhere MFT's License Servlet, a critical vulnerability affecting GoAnywhere MFT from Fortra. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 8 public PoC repositories reported; 2 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 9.8 describes technical severity, while EPSS 100% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.