How severe is CVE-2025-30406?

CVE-2025-30406 has a CVSS score of 9/10, rated CRITICAL. Immediate patching is strongly recommended.

Which products are affected by CVE-2025-30406?

Affected package information for CVE-2025-30406 is not yet fully mapped. Check the official advisory links for details.

How do I patch CVE-2025-30406?

Apply the gladinet centrestack security patch or hotfix for CVE-2025-30406 on the affected version, following the vendor advisory for your exact build.

How do I detect CVE-2025-30406 across my infrastructure?

Inventory every gladinet centrestack deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for remote code execution at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

How do I mitigate CVE-2025-30406 if there is no patch (or I can't update yet)?

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2025-30406?

O3 detects and blocks CVE-2025-30406 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Is CVE-2025-30406 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2025-30406, including . All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2025-30406?

CVE-2025-30406 has an EPSS (Exploit Prediction Scoring System) score of 93.8%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2025-30406 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2025-30406 (Gladinet CentreStack and Triofox Use of Hard-coded Cryptographic Key Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2025-04-08. CISA required all US federal civilian agencies to remediate this vulnerability by 2025-04-29. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2025-30406?

CVE-2025-30406 is classified as CWE-321 (CWE-321), Hard-coded Credentials (CWE-798). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2025-30406?

CVE-2025-30406 affects gladinet centrestack. Check the affected-products list on this page against your deployed version to confirm exposure.

Is there exploit tooling available for CVE-2025-30406?

A Nuclei detection template exists for CVE-2025-30406, meaning automated scanners can fingerprint it. 3 Metasploit modules reference CVE-2025-30406, which lowers the barrier to weaponization. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2025-30406 published, and has it been updated?

CVE-2025-30406 was published on April 3, 2025 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2025-04-08 — agencies required to remediate by 2025-04-29

CVE-2025-30406

CRITICAL

Gladinet CentreStack through 16.1.10296.56315 (fixed in 16.4.10315.56368) has a deserialization vulnerability due to the CentreStack portal's hardcoded machineKey use, as exploited…

Published

Apr 3, 2025

Updated

Jun 17, 2026

Affected

0 pkgs

Patched

None yet

Exploits

2 known

EPSS Exploitation Probability

via FIRST.org ↗

93.8%probability of exploitation in next 30 days

Very High Risk100th percentile+1.11%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

Gladinet CentreStack through 16.1.10296.56315 (fixed in 16.4.10315.56368) has a deserialization vulnerability due to the CentreStack portal's hardcoded machineKey use, as exploited in the wild in March 2025. This enables threat actors (who know the machineKey) to serialize a payload for server-side deserialization to achieve remote code execution. NOTE: a CentreStack admin can manually delete the machineKey defined in portal\web.config.

Affected Products

1 product · 1 configurations

Application

centrestackgladinet

< 16.4.10315.56368

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

mchklt/CVE-2025-30406

CVE-2025-30406 ViewState Exploit PoC

⭐ 90🍴 18Jul 2026

W01fh4cker/CVE-2025-30406

Exploit for CVE-2025-30406

⭐ 12🍴 4Dec 2025

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every gladinet centrestack deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for remote code execution at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Fix
Apply the gladinet centrestack security patch or hotfix for CVE-2025-30406 on the affected version, following the vendor advisory for your exact build.
Workarounds
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2025-30406 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2025-30406. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2025-30406 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2025-30406 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works