CVE-2025-35940: GFI Archiver · Use of Hard-coded Credentials
Affects GFI ArchiverSource CVE Database V5
Not known to be exploited · CVSS 8.1 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
NuGetarchiverpkg:nuget/archiverOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
In the interim, restrict network access to the ArchiverSpaApi endpoints using firewall rules or network segmentation to limit exposure to trusted internal IPs only. Implement Web Application Firewall (WAF) rules to detect and block suspicious JWT tokens or anomalous API requests. Conduct a thorough audit of existing JWT tokens and revoke any that may have been compromised. Review and enhance application security practices by eliminating hard-coded credentials and adopting secure key management solutions such as environment variables, secure vaults, or hardware security modules (HSMs). Monitor logs for unusual access patterns or failed authentication attempts. Additionally, consider deploying multi-factor authentication (MFA) on management interfaces and sensitive endpoints to add an extra layer of defense. Finally, educate development teams on secure coding practices to prevent recurrence of hard-coded secrets.
Description
The ArchiverSpaApi ASP.NET application uses a hard-coded JWT signing key. An unauthenticated remote attacker can generate and use a verifiable JWT token to access protected ArchiverSpaApi URL endpoints.