What is CVE-2025-54314?

CVE-2025-54314 is a high-severity OS command injection vulnerability in thor (rubygems), affecting versions < 1.4.0. It is fixed in 1.4.0. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.

How severe is CVE-2025-54314?

CVE-2025-54314 has a CVSS score of 7.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of thor are affected by CVE-2025-54314?

thor (rubygems) versions < 1.4.0 is affected.

Is there a fix for CVE-2025-54314?

Yes. CVE-2025-54314 is fixed in 1.4.0. Upgrade to this version or later.

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

Whether CVE-2025-54314 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-54314 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.

CVE-2025-54314 in thor

Q: How severe is CVE-2025-54314?

CVE-2025-54314 has a CVSS score of 7.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of thor are affected by CVE-2025-54314?

thor (rubygems) versions < 1.4.0 is affected.

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

Yes. CVE-2025-54314 is fixed in 1.4.0. Upgrade to this version or later.

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

Whether CVE-2025-54314 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-54314 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-54314?

Upgrade thor to 1.4.0 or later.

Summary

Withdrawn Advisory: Thor can construct an unsafe shell command from library input.

Withdrawn Advisory

This advisory has been withdrawn because the method described can only be used with arguments that are controlled by Thor, and an external attacker cannot access the functionality described in the body of the CVE. This link is maintained to preserve external references.

Original Description

Thor before 1.4.0 can construct an unsafe shell command from library input.

Impact

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

CVE-2025-54314 has a CVSS score of 7.8 (High). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.4.0); upgrading removes the vulnerable code path.

Affected versions

thor (< 1.4.0)

Security releases

thor → 1.4.0 (rubygems)

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

Upgrade thor to 1.4.0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2025-54314? CVE-2025-54314 is a high-severity OS command injection vulnerability in thor (rubygems), affecting versions < 1.4.0. It is fixed in 1.4.0. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
How severe is CVE-2025-54314? CVE-2025-54314 has a CVSS score of 7.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of thor are affected by CVE-2025-54314? thor (rubygems) versions < 1.4.0 is affected.
Is there a fix for CVE-2025-54314? Yes. CVE-2025-54314 is fixed in 1.4.0. Upgrade to this version or later.
Is CVE-2025-54314 exploitable, and should I be worried? Whether CVE-2025-54314 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-54314 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-54314? Upgrade thor to 1.4.0 or later.