What is CVE-2025-48756?

CVE-2025-48756 is a low-severity type confusion vulnerability in scsir (rust), affecting versions <= 0.2.0. No fixed version is listed yet. An object is accessed using a type that is incompatible with its actual type, causing the runtime to interpret memory incorrectly.

How severe is CVE-2025-48756?

CVE-2025-48756 has a CVSS score of 2.9 (Low). 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 scsir are affected by CVE-2025-48756?

scsir (rust) versions <= 0.2.0 is affected.

Is there a fix for CVE-2025-48756?

No fixed version is listed for CVE-2025-48756 yet. Monitor the advisory for updates and apply mitigations in the interim.

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

Whether CVE-2025-48756 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-48756 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-48756 in scsir

Q: How severe is CVE-2025-48756?

CVE-2025-48756 has a CVSS score of 2.9 (Low). 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 scsir are affected by CVE-2025-48756?

scsir (rust) versions <= 0.2.0 is affected.

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

No fixed version is listed for CVE-2025-48756 yet. Monitor the advisory for updates and apply mitigations in the interim.

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

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

No fixed version is listed yet. In the interim: Keep the dependency up to date. In native-code projects, use strict type checking and avoid unsafe casts.

Summary

SCSIR has a Potential Unsound Issue in WriteSameCommand

In group_number in the scsir crate 0.2.0 for Rust, there can be an overflow because a hardware device may expect a small number of bits (e.g., 5 bits) for group number.

Impact

An object is accessed using a type that is incompatible with its actual type, causing the runtime to interpret memory incorrectly. Typical impact: memory safety violations, unexpected behavior, or code execution.

CVE-2025-48756 has a CVSS score of 2.9 (Low). The vector is requires local access, no 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. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.

Affected versions

scsir (<= 0.2.0)

Security releases

Not available

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

No fixed version is listed for CVE-2025-48756 yet.

In the interim: Keep the dependency up to date. In native-code projects, use strict type checking and avoid unsafe casts.

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

Frequently Asked Questions

What is CVE-2025-48756? CVE-2025-48756 is a low-severity type confusion vulnerability in scsir (rust), affecting versions <= 0.2.0. No fixed version is listed yet. An object is accessed using a type that is incompatible with its actual type, causing the runtime to interpret memory incorrectly.
How severe is CVE-2025-48756? CVE-2025-48756 has a CVSS score of 2.9 (Low). 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 scsir are affected by CVE-2025-48756? scsir (rust) versions <= 0.2.0 is affected.
Is there a fix for CVE-2025-48756? No fixed version is listed for CVE-2025-48756 yet. Monitor the advisory for updates and apply mitigations in the interim.
Is CVE-2025-48756 exploitable, and should I be worried? Whether CVE-2025-48756 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-48756 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-48756? No fixed version is listed yet. In the interim: Keep the dependency up to date. In native-code projects, use strict type checking and avoid unsafe casts.