cve.bz

CVE-2026-41416 teluu pjsip: Year 2038 problem, Y2K38, Y2038, Epochalypse

8.1 highEPSS 0.3%Fix available

High (8.1) in teluu pjsip. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
PJSIP is a free and open source multimedia communication library written in C. In 2.16 and earlier, there is an integer overflow in media stream buffer size calculation when processing SDP with asymmetric ptime configuration. The overflow may result in an undersized buffer allocation, which can lead to unexpected application termination or memory corruption This vulnerability is fixed in 2.17.

Severity

CVSS 4.0

8.1 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 21st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-04-27. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-190 Integer Overflow or Wraparound (Year 2038 problem, Y2K38, Y2038, Epochalypse)
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-41416 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-41416?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-41416?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-41416 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
teluu:pjsipbefore 2.17

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14asterisk1:22.10.0+dfsg+~cs6.17.60671434-1DEBIAN-CVE-2026-41416
Ubuntu18.04:LTS, 20.04:LTS, 22.04:LTS and 4 moreasteriskno fix listedUBUNTU-CVE-2026-41416
UbuntuPro:16.04:LTSasterisk, pjprojectno fix listedUBUNTU-CVE-2026-41416
UbuntuPro:18.04:LTSpjprojectno fix listedUBUNTU-CVE-2026-41416

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON