CVE-2026-42225
TLS cert verification bypass in PJSIP (GnuTLS) before 2.17.
Is CVE-2026-42225 being exploited?
Not confirmed. CVE-2026-42225 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.16% probability of exploitation in the next 30 days.
How severe is CVE-2026-42225?
CVE-2026-42225 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-42225?
Yes. A fix has been recorded for CVE-2026-42225. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-42225 affect?
CVE-2026-42225 affects PJSIP (pre-2.17 on GnuTLS). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-42225?
Upgrade to PJSIP 2.17+
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
TLS verification bypass enables MITM; could allow remote code execution in apps using PJSIP that process untrusted data.
Patch when possible
- affected< 2.17
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.