VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

libosdp: vulnerability history, versions and safety

libosdp is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 1 release, from Mar 2024 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded M2 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all libosdp vulnerabilities

Vulert verdict on libosdp 3.2.7 i

Updated on 23 Oct 2026

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

Package health score 77/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Moderate

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

  • Current release 3.2.7 — unaffected i
  • Vulnerabilities on record 4 over 2 years · 2 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 6.5 i
  • With no published fix 0 i
  • Stars 198 i
  • Last release 1 month ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by PyPI, 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 libosdp, 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
3.2.7 25 Aug 2026 none non-standard — Details →
3.2.6 04 Aug 2026 none non-standard — Details →
3.2.5 10 Jul 2026 none non-standard — Details →
3.2.3 09 Jul 2026 none non-standard — Details →
3.1.2 14 Jun 2026 none non-standard — Details →
3.2.0 18 Mar 2026 none non-standard — Details →
3.1.0 25 Sep 2025 none non-standard — Details →
3.0.8 12 Nov 2024 none non-standard — Details →
3.0.7 12 Nov 2024 none non-standard — Details →
3.0.6 10 May 2024 none non-standard — Details →
3.0.5 23 Mar 2024 none non-standard — Details →
3.0.4 19 Mar 2024 none non-standard — Details →
3.0.3 13 Mar 2024 none non-standard — Details →
3.0.2 09 Mar 2024 none non-standard — Details →
3.0.1 20 Feb 2024 none non-standard — Details →
3.0.0 14 Feb 2024 none non-standard — Details →
2.4.0 22 Nov 2023 M1 U1 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 2
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for libosdp

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Null Pointer Dereference Vulnerability in LibOSDP 6.5 medium 2.4.0 08 Mar 2024
CVE-2024-52296: libosdp Denial of Service Vulnerability Due to Null Pointer Dereference 6.5 medium 2.4.0 07 Jul 2026
Vulnerability in libosdp: RMAC Revert to the Beginning of the Session 5.1 medium 3.0.0 08 Mar 2024
CVE-2024-52288: libosdp Replay Attack Vulnerability in Secure Communication 5.1 medium 3.0.0 07 Jul 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 libosdp

Is libosdp safe to use?

Vulert records 4 vulnerabilities for libosdp in PyPI: 0 critical, 0 high, 2 medium and 0 low, plus 2 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is libosdp's Vulert package health score?

Vulert scores libosdp 77/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 libosdp affected?

No. 3.2.7, 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.

Which version of libosdp should I use?

3.2.7 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 libosdp have?

4 vulnerabilities are recorded for libosdp in the PyPI ecosystem: 0 critical, 0 high, 2 medium and 0 low, plus 2 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new libosdp vulnerabilities disclosed?

2 vulnerabilities were recorded for libosdp in the last 12 months, and the oldest entry in this database dates to 08 Mar 2024. 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 libosdp 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 libosdp for upcoming vulnerabilities?

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