What is CVE-2025-59163?

CVE-2025-59163 is a low-severity security vulnerability in github.com/safedep/vet (go), affecting versions < 1.12.5. It is fixed in 1.12.5.

Which versions of github.com/safedep/vet are affected by CVE-2025-59163?

github.com/safedep/vet (go) versions < 1.12.5 is affected.

Is there a fix for CVE-2025-59163?

Yes. CVE-2025-59163 is fixed in 1.12.5. Upgrade to this version or later.

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

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

Upgrade github.com/safedep/vet to 1.12.5 or later.

CVE-2025-59163 in github.com/safedep/vet

Q: Which versions of github.com/safedep/vet are affected by CVE-2025-59163?

github.com/safedep/vet (go) versions < 1.12.5 is affected.

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

Yes. CVE-2025-59163 is fixed in 1.12.5. Upgrade to this version or later.

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

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

Upgrade github.com/safedep/vet to 1.12.5 or later.

Summary

vet MCP Server SSE Transport DNS Rebinding Vulnerability

SafeDep vet is vulnerable to a DNS rebinding attack due to lack of HTTP Host and Origin header validation.

To exploit this vulnerability following conditions must be met:

A vet scan is executed and reports are saved as sqlite3 database
A vet MCP server is running on default port with SSE transport that has access to the report database
The attacker lures the victim to attacker controlled website
Attacker leverages DNS rebinding to access vet SSE server on 127.0.0.1 through the website
Attacker uses MCP tools to read information from report database

Workarounds

Use stdio (default) transport for SSE server

Impact

Data from vet scan sqlite3 database may be exposed to remote attackers when vet is used as an MCP server in SSE mode with default ports through the sqlite3 query MCP tool.

Affected versions

github.com/safedep/vet (< 1.12.5)

Security releases

github.com/safedep/vet → 1.12.5 (go)

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

v1.12.5 is released that patches the issue with Host and Origin header allow list and validation

Frequently Asked Questions

What is CVE-2025-59163? CVE-2025-59163 is a low-severity security vulnerability in github.com/safedep/vet (go), affecting versions < 1.12.5. It is fixed in 1.12.5.
Which versions of github.com/safedep/vet are affected by CVE-2025-59163? github.com/safedep/vet (go) versions < 1.12.5 is affected.
Is there a fix for CVE-2025-59163? Yes. CVE-2025-59163 is fixed in 1.12.5. Upgrade to this version or later.
Is CVE-2025-59163 exploitable, and should I be worried? Whether CVE-2025-59163 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-59163 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-59163? Upgrade github.com/safedep/vet to 1.12.5 or later.