Which versions of tabby-ssh are affected by CVE-2024-48460?

tabby-ssh (npm) versions < 1.0.214 is affected.

Is there a fix for CVE-2024-48460?

Yes. CVE-2024-48460 is fixed in 1.0.214. Upgrade to this version or later.

Is CVE-2024-48460 exploitable, and should I be worried?

Whether CVE-2024-48460 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-2024-48460 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-2024-48460 in tabby-ssh

Q: What is CVE-2024-48460?

CVE-2024-48460 is a high-severity security vulnerability in tabby-ssh (npm), affecting versions < 1.0.214. It is fixed in 1.0.214.

Q: Is there a fix for CVE-2024-48460?

Yes. CVE-2024-48460 is fixed in 1.0.214. Upgrade to this version or later.

Q: Is CVE-2024-48460 exploitable, and should I be worried?

Whether CVE-2024-48460 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-2024-48460 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-2024-48460?

Upgrade tabby-ssh to 1.0.214 or later.

CVE-2024-48460

CVE-2024-48460 is a high-severity security vulnerability in tabby-ssh (npm), affecting versions < 1.0.214. It is fixed in 1.0.214.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Eugeny Tabby Sends Password Despite Host Key Verification Failure

An issue in Eugeny Tabby 1.0.213 allows a remote attacker to obtain sensitive information via the server and sends the SSH username and password even when the host key verification fails.

Impact

Affected versions

tabby-ssh (< 1.0.214)

Security releases

tabby-ssh → 1.0.214 (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

Upgrade tabby-ssh to 1.0.214 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-2024-48460? CVE-2024-48460 is a high-severity security vulnerability in tabby-ssh (npm), affecting versions < 1.0.214. It is fixed in 1.0.214.
Which versions of tabby-ssh are affected by CVE-2024-48460? tabby-ssh (npm) versions < 1.0.214 is affected.
Is there a fix for CVE-2024-48460? Yes. CVE-2024-48460 is fixed in 1.0.214. Upgrade to this version or later.
Is CVE-2024-48460 exploitable, and should I be worried? Whether CVE-2024-48460 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-2024-48460 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-2024-48460? Upgrade tabby-ssh to 1.0.214 or later.