VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

pjsip: vulnerability history, versions and safety

pjsip is a package in the OSS-Fuzz ecosystem. Vulert records 3 vulnerabilities for it across 3 affected ranges, from May 2024 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded H1 M2
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 05 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all pjsip vulnerabilities

Vulert verdict on pjsip i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 05 Jun 2026. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 3 vulnerabilities on record across 2 years, 2 in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 3 over 2 years · 2 in the last year i
  • Latest disclosure 05 Jun 2026 i
  • Highest CVSS n/a i
  • With no published fix 0 i

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

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
from fea85c46fd3bc3d51fe5eda55f8b4b73e4896a5f up to 83aa1379cf1692eb8d06bc20612cb1ab95060c69 (exclusive) 1
from f38d781a82a2b51b51a9996d4d76bdd8e69304d4 up to 24ac5875ffdff3f287e495e3ce81ae1d11777f3e (exclusive) 1
from 2f76bbaf5ed59c426fffec578fa15e4d1fb0a682 up to d0cbf57aca90f4722194c4e0d94ef0b236bb2489 (exclusive) 1

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for pjsip

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Use-of-uninitialized-value in encode_base64_differential in pjsip N/A medium 24ac5875ffdff3f287e495e3ce81ae1d11777f3e 08 May 2024
Uninitialized Value Vulnerability in pjsip Package N/A medium 83aa1379cf1692eb8d06bc20612cb1ab95060c69 03 Mar 2026
Heap Buffer Overflow Vulnerability in PJSIP Package N/A high d0cbf57aca90f4722194c4e0d94ef0b236bb2489 05 Jun 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 pjsip

Is pjsip safe to use?

Vulert records 3 vulnerabilities for pjsip in OSS-Fuzz: 0 critical, 1 high, 2 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.

How many vulnerabilities does pjsip have?

3 vulnerabilities are recorded for pjsip in the OSS-Fuzz ecosystem: 0 critical, 1 high, 2 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 pjsip vulnerabilities disclosed?

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

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