Skip to main content
VulnerabilityPublished

CVE-2025-47771: powsybl-core · Deserialization of Untrusted Data

Affects powsybl-coreSource CVE Database V5

0

Not known to be exploited · CVSS 8.1 High : upgrade to 6.7.2 soon.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 6.7.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade com.powsybl/powsybl-math to 6.7.2.

Affected software

ProductAffectedFixed in
Mavencom.powsybl/powsybl-mathpkg:maven/com.powsybl/powsybl-mathOther threatsAffected
  • >=6.3.0 <6.7.2
Fixed in
  • 6.7.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediate upgrade to powsybl-math version 6.7.2 or later, which contains the patch for this vulnerability, is the most effective mitigation.
  2. Until an upgrade is possible, disable or avoid using the SparseMatrix.read(...) deserialization methods entirely to prevent exposure to untrusted input streams.
  3. Implement strict input validation and sanitization on any data streams fed into the SparseMatrix deserialization process to reduce risk.
  4. Employ network segmentation and strict access controls around systems running PowSyBl to limit exposure to untrusted networks and reduce attack surface.
  5. Monitor logs and network traffic for unusual deserialization attempts or malformed input streams targeting the SparseMatrix class.
  6. Conduct thorough security assessments and penetration testing focused on deserialization vectors within power system software environments.
  7. Establish incident response plans specifically addressing potential compromises of power system modeling tools to enable rapid containment and recovery.
  8. Collaborate with vendors and industry groups to share threat intelligence and best practices related to PowSyBl and similar frameworks.

Description

PowSyBl (Power System Blocks) is a framework to build power system oriented software. In versions 6.3.0 to 6.7.1, there is a deserialization issue in the read method of the SparseMatrix class that can lead to a wide range of privilege escalations depending on the circumstances. This method takes in an InputStream and returns a SparseMatrix object. This issue has been patched in com.powsybl:powsybl-math: 6.7.2. A workaround for this issue involves not using SparseMatrix deserialization (SparseMatrix.read(...) methods).

References

Community reviews

Loading reviews…