Vulnerability Database · Maven · Package report

com.powsybl:powsybl-math: vulnerability history, versions and safety

com.powsybl:powsybl-math is a package in the Maven ecosystem. Vulert records 1 vulnerability for it across 15 releases, first recorded in Jun 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on com.powsybl:powsybl-math 7.4.2 i

Updated on 23 Oct 2026

Good news: 7.4.2, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 78/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

What to do: Stay on 7.4.2 or newer. This can change: a vulnerability disclosed tomorrow can affect 7.4.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 7.4.2 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 19 Jun 2025 i
  • Highest CVSS 8.1 i
  • With no published fix 0 i
  • Stars 190 i
  • OpenSSF scorecard 7/10 i
  • Last release this month i
  • Licence non-standard i

Version list, release dates, licence and dependants published by Maven Central, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for com.powsybl:powsybl-math, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
7.4.2 23 Oct 2026 none non-standard — Details →
7.4.0 15 Oct 2026 none non-standard — Details →
7.4.0-RC2 08 Oct 2026 none non-standard — Details →
7.3.1 01 Oct 2026 none non-standard — Details →
7.4.0-RC1 25 Sep 2026 none non-standard — Details →
7.3.0 29 Jun 2026 none non-standard — Details →
7.2.2 24 Jun 2026 none non-standard — Details →
7.3.0-RC2 22 Jun 2026 none non-standard — Details →
7.2.1 01 Apr 2026 none non-standard — Details →
7.2.0 26 Mar 2026 none non-standard — Details →
7.2.0-RC1 19 Mar 2026 none non-standard — Details →
7.1.2 06 Mar 2026 none non-standard — Details →
7.1.1 12 Jan 2026 none non-standard — Details →
7.1.0 04 Dec 2025 none non-standard — Details →
7.1.0-RC1 27 Nov 2025 none non-standard — Details →
7.0.1 22 Oct 2025 none non-standard — Details →
7.0.0 14 Oct 2025 none non-standard — Details →
7.0.0-RC1 07 Oct 2025 none non-standard — Details →
6.8.1 16 Jul 2025 none non-standard — Details →
6.8.0 09 Jul 2025 none non-standard — Details →
6.8.0-RC2 02 Jul 2025 none non-standard — Details →
6.7.2 19 Jun 2025 none non-standard — Details →
6.7.1 06 May 2025 H1 non-standard Yes Details →
6.7.0 25 Mar 2025 H1 non-standard Yes Details →
6.7.0-RC1 18 Mar 2025 H1 non-standard Yes Details →
6.6.1 23 Jan 2025 H1 non-standard Yes Details →
6.6.0 12 Dec 2024 H1 non-standard Yes Details →
6.6.0-RC1 04 Dec 2024 H1 non-standard Yes Details →
6.5.1 31 Oct 2024 H1 non-standard Yes Details →
6.5.0 11 Oct 2024 H1 non-standard Yes Details →
6.5.0-RC1 01 Oct 2024 H1 non-standard Yes Details →
6.4.1 11 Jul 2024 H1 non-standard Yes Details →
6.4.0 01 Jul 2024 H1 non-standard Yes Details →
6.4.0-RC2 24 Jun 2024 H1 non-standard Yes Details →
6.3.2 11 Jun 2024 H1 non-standard Yes Details →
6.3.1 02 May 2024 H1 non-standard Yes Details →
6.3.0 29 Mar 2024 H1 non-standard Yes Details →
6.2.4 25 Mar 2024 none non-standard — Details →
6.3.0-alpha-1 19 Mar 2024 none non-standard — Details →
6.2.3 06 Mar 2024 none non-standard — Details →
6.2.2 23 Feb 2024 none non-standard — Details →
6.2.1 15 Feb 2024 none non-standard — Details →
6.2.0 29 Jan 2024 none non-standard — Details →
6.1.2 23 Jan 2024 none non-standard — Details →
6.2.0-RC1 19 Jan 2024 none non-standard — Details →
6.1.1 20 Dec 2023 none non-standard — Details →
6.1.0 06 Dec 2023 none non-standard — Details →
6.0.3 04 Dec 2023 none non-standard — Details →
6.1.0-alpha-1 22 Nov 2023 none non-standard — Details →
6.0.2 13 Nov 2023 none non-standard — Details →
6.0.1 06 Oct 2023 none non-standard — Details →
6.0.0 28 Sep 2023 none non-standard — Details →
6.0.0-RC1 21 Sep 2023 none non-standard — Details →
5.3.2 20 Jun 2023 none non-standard — Details →
5.3.1 12 Jun 2023 none non-standard — Details →
5.3.0 06 Jun 2023 none non-standard — Details →
5.3.0-alpha-2 31 May 2023 none non-standard — Details →
5.3.0-alpha-1 25 May 2023 none non-standard — Details →
5.2.1 14 Apr 2023 none non-standard — Details →
5.2.0 30 Mar 2023 none non-standard — Details →
5.2.0-RC1 15 Mar 2023 none non-standard — Details →
5.2.0-alpha-1 16 Feb 2023 none non-standard — Details →
5.1.1 02 Feb 2023 none non-standard — Details →
5.1.0 30 Jan 2023 none non-standard — Details →
5.1.0-RC1 17 Jan 2023 none non-standard — Details →
4.10.2 17 Nov 2022 none non-standard — Details →
5.0.0 15 Nov 2022 none non-standard — Details →
5.0.0-RC1 04 Nov 2022 none non-standard — Details →
4.10.1 19 Sep 2022 none non-standard — Details →
4.10.0 14 Sep 2022 none non-standard — Details →
4.10.0-RC1 08 Sep 2022 none non-standard — Details →
4.10.0-alpha-1 18 Jul 2022 none non-standard — Details →
4.9.2 07 Jul 2022 none non-standard — Details →
4.9.1 27 Jun 2022 none non-standard — Details →
4.9.0 13 Jun 2022 none non-standard — Details →
4.9.0-RC1 03 Jun 2022 none non-standard — Details →
4.8.0 14 Apr 2022 none non-standard — Details →
4.8.0-RC2 12 Apr 2022 none non-standard — Details →
4.8.0-RC1 01 Apr 2022 none non-standard — Details →
4.7.0 28 Feb 2022 none non-standard — Details →
4.7.0-RC2 23 Feb 2022 none non-standard — Details →
4.7.0-RC1 16 Feb 2022 none non-standard — Details →
4.6.1 28 Jan 2022 none non-standard — Details →
4.6.0 05 Jan 2022 none non-standard — Details →
4.6.0-RC1 15 Dec 2021 none non-standard — Details →
4.5.1 18 Nov 2021 none non-standard — Details →
4.5.0 10 Nov 2021 none non-standard — Details →
4.5.0-RC1 03 Nov 2021 none non-standard — Details →
3.7.2 27 Sep 2021 none non-standard — Details →
4.4.0 22 Sep 2021 none non-standard — Details →
4.4.0-RC1 15 Sep 2021 none non-standard — Details →
4.3.1 15 Jul 2021 none non-standard — Details →
4.3.0 15 Jul 2021 none non-standard — Details →
4.3.0-RC2 07 Jul 2021 none non-standard — Details →
4.3.0-RC1 28 Jun 2021 none non-standard — Details →
4.3.0-alpha-1 14 Jun 2021 none non-standard — Details →
4.2.0 25 May 2021 none non-standard — Details →
4.2.0-RC1 17 May 2021 none non-standard — Details →
4.1.2 28 Apr 2021 none non-standard — Details →
4.1.1 19 Apr 2021 none non-standard — Details →
4.1.0 08 Apr 2021 none — — Details →
3.8.1 15 Feb 2021 none — — Details →
4.0.1 11 Feb 2021 none — — Details →
4.0.0 05 Feb 2021 none — — Details →
4.0.0-RC2 26 Jan 2021 none — — Details →
4.0.0-RC1 20 Jan 2021 none — — Details →
3.8.0 02 Dec 2020 none — — Details →
3.8.0-RC1 16 Nov 2020 none — — Details →
3.7.1 16 Oct 2020 none — — Details →
3.3.2 16 Oct 2020 none — — Details →
3.7.0 14 Oct 2020 none — — Details →
3.6.0 09 Sep 2020 none — — Details →
3.3.1 29 Jul 2020 none — — Details →
3.5.0 29 Jul 2020 none — — Details →
3.4.0 17 Jun 2020 none — — Details →
3.3.0 29 Apr 2020 none — — Details →
3.2.0 28 Feb 2020 none — — Details →
3.1.0 08 Jan 2020 none — — Details →
3.0.0 23 Oct 2019 none — — Details →
2.6.1 14 Oct 2019 none — — Details →

The newest 120 of 132 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for com.powsybl:powsybl-math

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About com.powsybl:powsybl-math

Is com.powsybl:powsybl-math safe to use?

Vulert records 1 vulnerabilities for com.powsybl:powsybl-math in Maven: 0 critical, 1 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is com.powsybl:powsybl-math's Vulert package health score?

Vulert scores com.powsybl:powsybl-math 78/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of com.powsybl:powsybl-math affected?

No. 7.4.2, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does com.powsybl:powsybl-math have?

1 vulnerability is recorded for com.powsybl:powsybl-math in the Maven ecosystem: 0 critical, 1 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new com.powsybl:powsybl-math vulnerabilities disclosed?

0 vulnerabilities were recorded for com.powsybl:powsybl-math in the last 12 months, and the oldest entry in this database dates to 19 Jun 2025. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of com.powsybl:powsybl-math are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor com.powsybl:powsybl-math for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the com.powsybl:powsybl-math version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.