dbcve.org
PjsipApplication

CVE-2026-25994

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-11
Fix available
A fix is available. Upgrade to after 2.16 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
PJSIP is a free and open source multimedia communication library written in C. In 2.16 and earlier, a buffer overflow vulnerability exists in PJNATH ICE Session when processing credentials with excessively long usernames.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A buffer overflow vulnerability exists in PJSIP's PJNATH ICE Session component when processing credentials containing excessively long usernames. The flaw affects versions 2.16 and earlier and could allow remote attackers to execute arbitrary code or cause denial of service by providing maliciously long credential data.

MitigationUpgrade PJSIP to a version beyond 2.16 that addresses this vulnerability. Additionally, implement input validation to enforce reasonable maximum length limits on usernames before passing them to the ICE session credential processing routines.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PjsipApplication
Affected:<= 2.16

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed PJSIP version
    Locate the PJSIP library files (typically libpjsip.so, pjsip.dll, or similar) and query their version information using system utilities or check version headers if compiling from source
    Affected if The installed version is 2.16 or earlier
  2. Confirm PJNATH component presence
    Check for the presence of the PJNATH library (libpjnath.so, pjnath.dll, or similar) which contains the ICE Session functionality
    Affected if PJNATH library is present in the environment
  3. Determine if ICE is enabled
    Review application configuration or code to identify if ICE (Interactive Connectivity Establishment) sessions are being created or processed
    Affected if ICE session functionality is actively used
  4. Check credential configuration
    Inspect configuration files or application code where ICE credentials are defined, looking for username fields in credential objects passed to the ICE session
    Affected if ICE credentials with username fields are configured or processed
  5. Verify username length handling
    Examine how credential usernames are handled before being processed by the ICE session component, looking for any length validation or limits
    Affected if No length validation exists on credential usernames or excessively long usernames can be passed to the ICE session

The environment is affected if PJSIP version 2.16 or earlier is installed, PJNATH with ICE sessions is in use, and credential usernames can be provided without length restriction.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2.16
Vendor patch github.com →
Interim mitigation

Upgrade PJSIP to a version beyond 2.16 that addresses this vulnerability. Additionally, implement input validation to enforce reasonable maximum length limits on usernames before passing them to the ICE session credential processing routines.

Recommended fix Moderate confidence
  1. Obtain the fix from the vendor commit at https://github.com/pjsip/pjproject/commit/063b3a155f163cc5a9a1df2c56b6720fd3a0dbb0
  2. Review the patch to understand the vulnerability fix addressing the buffer overflow in PJNATH ICE Session when processing credentials with excessively long usernames
  3. Apply the patch to the pjproject source code
  4. Rebuild the PJSIP library with the patched code
  5. Redeploy the updated library
  6. Verify the fix is properly applied and test ICE credential processing functionality

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pjsip Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25994 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-25994 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data