CVE-2025-14611
Gladinet CentreStack and Triofox prior to version 16.12.10420.56791 used hardcoded values for their implementation of the AES cryptoscheme. This degrades security for public exposed endpoints that may make use of it and may offer arbitrary local file inclusion when provided a specially crafted request without authentication. This opens the door for future exploitation and can be leveraged with previous vulnerabilities to gain a full system compromise.
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? No. Hard-coded credentials let attackers log in normally. A WAF cannot tell their logins from real ones.
Also consider: patch · rotate
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2025-14611 being exploited?
Yes. CVE-2025-14611 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2025-14611?
CVE-2025-14611 is rated Critical with a CVSS score of 9.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-2025-14611?
Not known from our data. No patch reference has been recorded for CVE-2025-14611, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2025-14611 affect?
CVE-2025-14611 affects gladinet:centrestack, gladinet:triofox. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected< 16.12.10420.56791
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.
public exploits
Unvetted proof-of-concept code on GitHub: 1 Metasploit module · 1 GitHub proof of concept · 1 Nuclei template
- auxiliary/gather/gladinet_storage_access_ticket_forge · auxiliary · normal
- Gladinet CentreStack & Triofox - Hardcoded Credentials · detection template · critical
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 16 Dec 2025 (SSVC 2.0.3).
timeline
- 12 Dec 2025Published
- 15 Dec 2025Added to CISA KEV (exploited in the wild) · 2 days later
- 16 Dec 2025CISA SSVC assessment: exploitation active · 1 day later
- 29 Dec 2025First proof-of-concept repository on GitHub (unvetted) · 13 days later
- 5 Jan 2026CISA remediation due date (US federal agencies) · 7 days later
- 26 Feb 2026CVE record last updated · 53 days later
- 2 Nov 2026Analysed by vulneraibility.com · 249 days (about 8 months) later
- Linkhuntress.com /blog/active-exploitation-gladinet-centrestack-triofox-insecure-cryptography-vul
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-14611
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Metasploit Framework: exploit and scanner modules
- Nuclei templates: detection templates
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.