CVE-2026-25994

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 1.9%, top 22% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 9.8Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
75(Track)
EG Risk 75/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
2%
EPSS %ILE
80%
KEV
Not listed

Published

February 11, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Sep 14, 2026
Patch available. Sources: github_commit, github.
github Patch Available

Buffer overflow in ICE with long username · Advisory · pjsip/pjproject · GitHub

https://github.com/pjsip/pjproject/security/advisories/GHSA-j29p-pvh2-pvqp
github_commit Patch Available

commit 063b3a155f16 (pjsip/pjproject)

Patch available: pjsip/pjproject 2.17 (contains commit 063b3a155f16)

https://github.com/pjsip/pjproject/commit/063b3a155f163cc5a9a1df2c56b6720fd3a0dbb0

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibpjsua2 (2.1.0.0.ast20130823-1+deb8u1ubuntu0.1~esm1) @ xenial2026-06-12ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
pjproject—2.17-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
asterisk1:16.16.1~dfsg+~2.10-1 ... 1:16.28.0~dfsg-0+deb11u9 (21 versions)1:16.28.0~dfsg-0+deb11u10—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
asterisk0.1.11-3 ... 1:22.9.0+dfsg+~cs6.16.60671434-1 (291 versions)1:22.10.0+dfsg+~cs6.17.60671434-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 185 total refreshes for this CVE.

  1. 2026-09-19 15:33 UTCOSV refresh
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-16 14:07 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-12 15:01 UTCEPSS rescore
  7. 2026-09-11 14:52 UTCEPSS rescore
  8. 2026-09-10 09:34 UTCEPSS rescore
  9. 2026-09-08 22:00 UTCEPSS rescore
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-04 05:06 UTCEPSS rescore
  14. 2026-09-02 14:11 UTCEPSS rescore
  15. 2026-09-01 13:53 UTCEPSS rescore
  16. 2026-09-01 04:39 UTCEPSS rescore
  17. 2026-08-31 19:04 UTCOSV refresh
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-28 21:41 UTCEPSS rescore
  21. 2026-08-27 14:25 UTCEPSS rescore
  22. 2026-08-26 14:46 UTCEPSS rescore
  23. 2026-08-25 13:48 UTCEPSS rescore
  24. 2026-08-23 00:19 UTCEPSS rescore
  25. 2026-08-21 23:49 UTCEPSS rescore
Show 75 more
  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-19 17:03 UTCEPSS rescore
  3. 2026-08-18 13:48 UTCEPSS rescore
  4. 2026-08-17 13:47 UTCEPSS rescore
  5. 2026-08-16 14:56 UTCEPSS rescore
  6. 2026-08-16 02:14 UTCEPSS rescore
  7. 2026-08-15 01:30 UTCEPSS rescore
  8. 2026-08-14 22:37 UTCVendor advisory
  9. 2026-08-14 14:07 UTCVendor advisory
  10. 2026-08-14 10:20 UTCEG score recompute
  11. 2026-08-14 10:20 UTCVendor advisory
  12. 2026-08-13 22:00 UTCEPSS rescore
  13. 2026-08-13 02:35 UTCEG score recompute
  14. 2026-08-13 02:35 UTCVendor advisory
  15. 2026-08-12 13:50 UTCEPSS rescore
  16. 2026-08-11 13:42 UTCEPSS rescore
  17. 2026-08-11 09:03 UTCEG score recompute
  18. 2026-08-11 09:03 UTCVendor advisory
  19. 2026-08-11 00:00 UTCEPSS rescore
  20. 2026-08-10 09:45 UTCVendor advisory
  21. 2026-08-10 02:25 UTCVendor advisory
  22. 2026-08-09 22:33 UTCVendor advisory
  23. 2026-08-09 18:46 UTCVendor advisory
  24. 2026-08-09 14:59 UTCEG score recompute
  25. 2026-08-09 14:59 UTCVendor advisory
  26. 2026-08-08 16:37 UTCEPSS rescore
  27. 2026-08-08 09:33 UTCVendor advisory
  28. 2026-08-08 05:46 UTCVendor advisory
  29. 2026-08-08 01:58 UTCVendor advisory
  30. 2026-08-07 22:09 UTCEG score recompute
  31. 2026-08-07 22:09 UTCVendor advisory
  32. 2026-08-06 13:46 UTCEPSS rescore
  33. 2026-08-06 07:46 UTCVendor advisory
  34. 2026-08-06 03:59 UTCEG score recompute
  35. 2026-08-06 03:59 UTCVendor advisory
  36. 2026-08-05 19:17 UTCEPSS rescore
  37. 2026-08-04 15:10 UTCEPSS rescore
  38. 2026-08-03 10:36 UTCEPSS rescore
  39. 2026-08-03 01:38 UTCVendor advisory
  40. 2026-08-02 20:47 UTCEG score recompute
  41. 2026-08-02 20:47 UTCVendor advisory
  42. 2026-08-02 02:26 UTCEPSS rescore
  43. 2026-08-01 04:16 UTCEPSS rescore
  44. 2026-07-30 16:27 UTCEPSS rescore
  45. 2026-07-30 01:30 UTCEPSS rescore
  46. 2026-07-28 15:36 UTCEPSS rescore
  47. 2026-07-26 14:54 UTCEPSS rescore
  48. 2026-07-26 14:54 UTCEPSS rescore
  49. 2026-07-25 14:18 UTCEPSS rescore
  50. 2026-07-25 14:17 UTCEPSS rescore
  51. 2026-07-24 14:17 UTCEPSS rescore
  52. 2026-07-23 14:18 UTCEPSS rescore
  53. 2026-07-23 14:18 UTCEPSS rescore
  54. 2026-07-23 03:07 UTCEG score recompute
  55. 2026-07-22 14:08 UTCEPSS rescore
  56. 2026-07-22 14:08 UTCEPSS rescore
  57. 2026-07-21 15:24 UTCEPSS rescore
  58. 2026-07-21 15:24 UTCEPSS rescore
  59. 2026-07-20 17:08 UTCEPSS rescore
  60. 2026-07-20 17:08 UTCEPSS rescore
  61. 2026-07-19 14:31 UTCEPSS rescore
  62. 2026-07-19 14:31 UTCEPSS rescore
  63. 2026-07-19 02:29 UTCEPSS rescore
  64. 2026-07-19 02:28 UTCEPSS rescore
  65. 2026-07-18 10:04 UTCEPSS rescore
  66. 2026-07-18 10:04 UTCEPSS rescore
  67. 2026-07-17 15:29 UTCOSV refresh
  68. 2026-07-16 17:03 UTCEPSS rescore
  69. 2026-07-16 17:03 UTCEPSS rescore
  70. 2026-07-15 16:57 UTCEPSS rescore
  71. 2026-07-15 16:57 UTCEPSS rescore
  72. 2026-07-15 02:00 UTCEPSS rescore
  73. 2026-07-15 02:00 UTCEPSS rescore
  74. 2026-07-13 22:30 UTCEPSS rescore
  75. 2026-07-13 06:13 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 GitHub PoC) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-52561
    First seen May 14, 2026

    PJPROJECT 2.16 - Heap Bufferoverflow

    Open source ↗
  • GitHub PoCVABISMO/cve-2026-25994_PJSIP
    First seen Apr 7, 2026

    PJSIP cve-2026-25994 BUFFER OVERFLOW POC

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-25994?
CVE-2026-25994 is a critical vulnerability published on February 11, 2026. 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.
When was CVE-2026-25994 disclosed?
CVE-2026-25994 was first published in the National Vulnerability Database on February 11, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-25994 actively exploited?
CVE-2026-25994 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 20.1% of all scored CVEs.
What is the CVSS score of CVE-2026-25994?
CVE-2026-25994 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-25994?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-25994, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-25994

Explore →

Is Your Infrastructure Affected by CVE-2026-25994?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs