VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

com.github.psi-probe:psi-probe-core: vulnerability history, versions and safety

com.github.psi-probe:psi-probe-core is a package in the Maven ecosystem. Vulert records 2 vulnerabilities for it across 47 releases, first recorded in Feb 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded L2
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
2 in the last 12 months

Most recent disclosure 27 Feb 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all com.github.psi-probe:psi-probe-core vulnerabilities

Vulert verdict on com.github.psi-probe:psi-probe-core 5.5.0 i

Updated on 23 Oct 2026

Careful: 5.5.0 has 2 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 5.5.0 — affected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 27 Feb 2026 i
  • Highest CVSS 6.3 i
  • With no published fix 2 i
  • Depended on by 3 packages i
  • Stars 1,330 i
  • OpenSSF scorecard 5/10 i
  • Last release 1 month ago i
  • Licence GPL-2.0 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.github.psi-probe:psi-probe-core, 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
4.7.0 21 Sep 2026 L2 GPL-2.0 No Details →
5.5.0 21 Sep 2026 L2 GPL-2.0 No Details →
4.6.0 13 Jun 2026 L2 GPL-2.0 No Details →
5.4.0 11 Jun 2026 L2 GPL-2.0 No Details →
4.5.0 03 Aug 2025 L2 GPL-2.0 No Details →
5.3.0 03 Aug 2025 L2 GPL-2.0 No Details →
5.2.1 18 May 2025 L2 GPL-2.0 No Details →
4.4.0 18 May 2025 L2 GPL-2.0 No Details →
5.2.0 18 May 2025 L2 GPL-2.0 No Details →
4.3.2 06 Mar 2025 L2 GPL-2.0 No Details →
4.3.1 14 Sep 2024 L2 GPL-2.0 No Details →
5.1.1 14 Sep 2024 L2 GPL-2.0 No Details →
4.3.0 19 Jul 2024 L2 GPL-2.0 No Details →
5.1.0 19 Jul 2024 L2 GPL-2.0 No Details →
5.0.0 12 May 2024 L2 GPL-2.0 No Details →
4.2.0 24 Apr 2024 L2 GPL-2.0 No Details →
4.1.5 07 Apr 2024 L2 GPL-2.0 No Details →
4.1.4 02 Mar 2024 L2 GPL-2.0 No Details →
4.1.3 23 Feb 2024 L2 GPL-2.0 No Details →
4.1.2 17 Feb 2024 L2 GPL-2.0 No Details →
4.1.1 15 Jan 2024 L2 GPL-2.0 No Details →
4.1.0 03 Dec 2023 L2 GPL-2.0 No Details →
4.0.0 02 Nov 2023 L2 GPL-2.0 No Details →
3.7.3 11 May 2023 L2 GPL-2.0 No Details →
3.7.2 13 Mar 2023 L2 GPL-2.0 No Details →
3.7.1 08 Dec 2022 L2 GPL-2.0 No Details →
3.7.0 28 Nov 2022 L2 GPL-2.0 No Details →
3.6.0 24 Jul 2022 L2 GPL-2.0 No Details →
3.5.9 02 Jun 2022 L2 GPL-2.0 No Details →
3.5.8 18 Apr 2022 L2 GPL-2.0 No Details →
3.5.7 17 Feb 2022 L2 GPL-2.0 No Details →
3.5.6 06 Dec 2021 L2 GPL-2.0 No Details →
3.5.5 12 Sep 2021 L2 GPL-2.0 No Details →
3.5.4 23 Mar 2021 L2 GPL-2.0 No Details →
3.5.3 14 Dec 2020 L2 GPL-2.0 No Details →
3.5.1 30 Aug 2020 L2 GPL-2.0 No Details →
3.5.0 22 May 2020 L2 GPL-2.0 No Details →
3.4.5 19 Feb 2020 L2 GPL-2.0 No Details →
3.4.4 19 Feb 2020 L2 GPL-2.0 No Details →
3.4.3 18 Feb 2020 L2 GPL-2.0 No Details →
3.4.2 21 Nov 2019 L2 GPL-2.0 No Details →
3.3.1 16 Sep 2019 L2 GPL-2.0 No Details →
3.3.0 08 May 2019 L2 GPL-2.0 No Details →
3.2.0 20 Dec 2018 L2 GPL-2.0 No Details →
3.1.0 18 Jun 2018 L2 GPL-2.0 No Details →
3.0.0 14 Apr 2018 L2 GPL-2.0 No Details →
3.0.0.RC2 21 Aug 2017 L2 GPL-2.0 No Details →

All 47 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for com.github.psi-probe:psi-probe-core

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-3270: PSI Probe Server-Side Request Forgery Vulnerability 6.3 low No fix published 27 Feb 2026
CVE-2026-3269: PSI Probe Denial of Service Vulnerability in psi-probe-core 4.3 low No fix published 27 Feb 2026

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.github.psi-probe:psi-probe-core

Is com.github.psi-probe:psi-probe-core safe to use?

Vulert records 2 vulnerabilities for com.github.psi-probe:psi-probe-core in Maven: 0 critical, 0 high, 0 medium and 2 low. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is com.github.psi-probe:psi-probe-core's Vulert package health score?

Vulert scores com.github.psi-probe:psi-probe-core 60/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of com.github.psi-probe:psi-probe-core affected?

Yes. 5.5.0, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of com.github.psi-probe:psi-probe-core should I use?

5.5.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does com.github.psi-probe:psi-probe-core have?

2 vulnerabilities are recorded for com.github.psi-probe:psi-probe-core in the Maven ecosystem: 0 critical, 0 high, 0 medium and 2 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new com.github.psi-probe:psi-probe-core vulnerabilities disclosed?

2 vulnerabilities were recorded for com.github.psi-probe:psi-probe-core in the last 12 months, and the oldest entry in this database dates to 27 Feb 2026. 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.github.psi-probe:psi-probe-core 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.github.psi-probe:psi-probe-core for upcoming vulnerabilities?

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