Summary
PowSyBl Core allows deserialization of untrusted SparseMatrix data
Am I impacted?
You are vulnerable if you import non-controlled serialized SparseMatrix objects.
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
Do not use SparseMatrix deserialization (SparseMatrix.read(...) methods).
References
Impact
What kind of vulnerability is it? Who is impacted?
This is a disclosure for a security vulnerability in the SparseMatrix class. The vulnerability is a deserialization issue that
can lead to a wide range of privilege escalations depending on the circumstances. The problematic area is the read method
of the SparseMatrix class.
This method takes in an InputStream and returns a SparseMatrix object. We consider this to be a method that can be
exposed to untrusted input in at least two use cases:
- A user can adopt this method in an application where users can submit an
InputStreamand the application parses it into
aSparseMatrix. This can be a multi-tenant application that hosts many different users perhaps with different privilege
levels. - A user adopts the method for a local tool but receives the
InputStreamfrom external sources.
Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect. Typical impact: arbitrary code execution or logic abuse.
Affected versions
Security releases
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 environmentNew to Kodem? Get a demo →Remediation advice
com.powsybl:powsybl-math:6.7.2 and higher
Frequently Asked Questions
- What is CVE-2025-47771? CVE-2025-47771 is a high-severity insecure deserialization vulnerability in com.powsybl:powsybl-math (maven), affecting versions >= 6.3.0, <= 6.7.1. It is fixed in 6.7.2. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.
- Which versions of com.powsybl:powsybl-math are affected by CVE-2025-47771? com.powsybl:powsybl-math (maven) versions >= 6.3.0, <= 6.7.1 is affected.
- Is there a fix for CVE-2025-47771? Yes. CVE-2025-47771 is fixed in 6.7.2. Upgrade to this version or later.
- Is CVE-2025-47771 exploitable, and should I be worried? Whether CVE-2025-47771 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-47771 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-47771? Upgrade
com.powsybl:powsybl-mathto 6.7.2 or later.