What is CVE-2025-62713?

CVE-2025-62713 is a high-severity OS command injection vulnerability in @kottster/server (npm), affecting versions >= 3.2.0, < 3.3.2. It is fixed in 3.3.2. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.

Which versions of @kottster/server are affected by CVE-2025-62713?

@kottster/server (npm) versions >= 3.2.0, < 3.3.2 is affected.

Is there a fix for CVE-2025-62713?

Yes. CVE-2025-62713 is fixed in 3.3.2. Upgrade to this version or later.

Is CVE-2025-62713 exploitable, and should I be worried?

Whether CVE-2025-62713 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-62713 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2025-62713?

Upgrade @kottster/server to 3.3.2 or later.

CVE-2025-62713 in @kottster/server

Q: Which versions of @kottster/server are affected by CVE-2025-62713?

@kottster/server (npm) versions >= 3.2.0, < 3.3.2 is affected.

Q: Is there a fix for CVE-2025-62713?

Yes. CVE-2025-62713 is fixed in 3.3.2. Upgrade to this version or later.

Q: Is CVE-2025-62713 exploitable, and should I be worried?

Whether CVE-2025-62713 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2025-62713 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2025-62713?

Upgrade @kottster/server to 3.3.2 or later.

Summary

Kottster app reinitialization can be re-triggered allowing command injection in development mode

Workarounds

Do not expose development servers to public networks or untrusted users
Use production mode for any deployment accessible from outside trusted environments

Credit

We sincerely thank Jeongwon Jo (@P0cas) from RedAlert for discovering and responsibly disclosing this vulnerability.

Impact

Development mode only. Kottster contains a pre-authentication remote code execution (RCE) vulnerability when running in development mode.

The vulnerability combines two issues:

The initApp action can be called repeatedly without checking if the app is already initialized, allowing attackers to create a new root admin account and obtain a JWT token
The installPackagesForDataSource action uses unescaped command arguments, enabling command injection

An attacker with access to a locally running development instance can chain these vulnerabilities to:

Reinitialize the application and receive a JWT token for a new root account
Use this token to authenticate
Execute arbitrary system commands through installPackagesForDataSource

Production deployments were never affected.

Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.

Affected versions

@kottster/server (>= 3.2.0, < 3.3.2)

Security releases

@kottster/server → 3.3.2 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Fixed in v3.3.2.

Specifically, @kottster/server v3.3.2 and @kottster/cli v3.3.2 address this vulnerability.

We recommend developers using earlier versions of @kottster/server and @kottster/cli update all the core packages to latest release:

npm install @kottster/common@latest @kottster/cli@latest @kottster/server@latest @kottster/react@latest

Frequently Asked Questions

What is CVE-2025-62713? CVE-2025-62713 is a high-severity OS command injection vulnerability in @kottster/server (npm), affecting versions >= 3.2.0, < 3.3.2. It is fixed in 3.3.2. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
Which versions of @kottster/server are affected by CVE-2025-62713? @kottster/server (npm) versions >= 3.2.0, < 3.3.2 is affected.
Is there a fix for CVE-2025-62713? Yes. CVE-2025-62713 is fixed in 3.3.2. Upgrade to this version or later.
Is CVE-2025-62713 exploitable, and should I be worried? Whether CVE-2025-62713 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-62713 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-62713? Upgrade @kottster/server to 3.3.2 or later.