OSV-2025-240
Security exception in com.powsybl.commons.xml.XmlUtil.lambda$skipSubElements$0
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=406332767
Crash type: Security exception
Crash state:
com.powsybl.commons.xml.XmlUtil.lambda$skipSubElements$0
com.powsybl.commons.xml.XmlUtil.readSubElements
com.powsybl.commons.xml.XmlUtil.skipSubElements
What each source reports
OSV No score
Security exception in com.powsybl.commons.xml.XmlUtil.lambda$skipSubElements$0
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=406332767
Crash type: Security exception
Crash state:
com.powsybl.commons.xml.XmlUtil.lambda$skipSubElements$0
com.powsybl.commons.xml.XmlUtil.readSubElements
com.powsybl.commons.xml.XmlUtil.skipSubElements
- Record
OSV-2025-240- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
powsybl-javaOSS-Fuzz |
Commit ranges | Not evaluated |
Not evaluated means the source gave git commits or a range we can't read, so we can't tell which releases are affected. A fixed version beside it is the source’s own claim.
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
OSV-2025-240 is a vulnerability with no CVSS score yet in powsybl-java, published March 28, 2025. No source lists public exploit code. A source reports a fix.