What is CVE-2025-14611?

CVE-2025-14611 is Gladinet CentreStack and TrioFox Hard Coded AES Keys. The supplied enrichment data classifies it as Credentials mapped to CWE-798 Use of Hard-coded Credentials.

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?

2 public PoC repositories reported; 1 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 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-14611 using CVSS 9.8, EPSS 53%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. 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: Tick (). 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 KEVcriticalCredentialspublic exploit

CVE-2025-14611

CVE-2025-14611 — Gladinet CentreStack and TrioFox Hard Coded AES Keys

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2025-14611 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.

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.

Published Dec 12, 2025Updated Jun 17, 2026Sources: NVD, Gladinet (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 Dec 15, 2025

EPSS

53%

ahead of 99% of scored CVEs

Affects

Gladinet

CentreStack and TrioFox

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

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 CentreStack and TrioFox to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

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 Jan 5, 2026 — passed 256 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
Gladinet	CentreStack and TrioFox	0 to < 16.12.10420.56791	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
9.8	CVSS 3.1	critical	3.9	5.9	NVD
7.1	CVSS 4.0	high	—	—	Gladinet (CNA)

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

Weakness & attack patterns

CWE-798Use of Hard-coded Credentials

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

CAPEC-70 · Try Common or Default Usernames and PasswordsCAPEC-191 · Read Sensitive Constants Within an Executable

T1552.001Unsecured Credentials: Credentials in files
T1078.001Valid Accounts: Default Accounts

CISA KEV details

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

CISAThat month →

Listed

Dec 15, 2025

Federal deadline

Jan 5, 2026

passed 256 days ago

Ransomware use

Unknown

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

1 of the 1 sampled are weaponized

Exploit entries

Exploit-DB and CTI exploit indexes

Social mentions

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

9 more posts on this CVEShowing 5 of 14 · 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 CentreStack and TrioFox.
Monitor for scanner or exploit-pattern traffic after 2 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPS

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.

Tick

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)
Jun 17, 2026 · NVD
2025
Cve is exploited pl4tyz/CVE-2025-14611-CentreStack-and-Triofox-full-Poc-Exploit
Dec 29, 2025 · SOCRadar CTI
Added to CISA KEV catalog
Dec 15, 2025 · CISA
Initial · CVE published
Dec 12, 2025 · NVD

Source activity

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

16×SVRS was changedDec 16, 2025 – Jan 19, 2026 · SOCRadar CTI
9×TweetsDec 16, 2025 – Apr 23, 2026 · SOCRadar CTI
2×ModifiedDec 16, 2025 · SOCRadar CTI
1×Github_Repos · Github repository created, pl4tyz/CVE-2025-14611-CentreStack-and-Triofox-full-Poc-ExploitDec 29, 2025 · SOCRadar CTI
1×1 time mentioned on 1 Telegram channelDec 18, 2025 · SOCRadar CTI

References

6 on the record

www.huntress.com/blog/active-exploitation-gladinet-centrestack-triofox-insecure-cryptography-vulnerability
Exploit, Third Party Advisory, NIST, GITHUB
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-14611
US Government Resource
www.centrestack.com/p/gce_latest_release.html
Vendor Advisory
access.triofox.com/releases_history/
Vendor Advisory
support.centrestack.com/hc/en-us/articles/360007159054-Hardening-the-CentreStack-Cluster#h_01JQRV57T37HJFQZKBZH9NBXQP
Vendor Advisory
nvd.nist.gov/vuln/detail/CVE-2025-14611
Vendor Advisory

Coverage

11 stories from the feeds we poll

6 more reports on this CVEShowing 5 of 11 · Vendor research and security press coverageUnlock free

Elsewhere on this site

Gladinetevery CVE for this vendor
December 2025what else CISA listed
Credentialssame class
CWE-798other 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.

No confirmed IOCs, IP addresses, domains, file hashes, or malware 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-14611 is Gladinet CentreStack and TrioFox Hard Coded AES Keys, a critical vulnerability affecting CentreStack and TrioFox from Gladinet. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 2 public PoC repositories reported; 1 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 53% 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.