CVE-2026-25237
RCE via preg_replace /e in PEAR bug email handling pre-1.33.0
Is CVE-2026-25237 being exploited?
Not confirmed. CVE-2026-25237 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.40% probability of exploitation in the next 30 days.
How severe is CVE-2026-25237?
CVE-2026-25237 is rated Critical with a CVSS score of 9.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-25237?
Yes. A fix has been recorded for CVE-2026-25237. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-25237 affect?
CVE-2026-25237 affects PEAR PHP framework <= 1.32.x, PHP apps using PEAR email handling. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-25237?
Upgrade to PEAR 1.33.0+
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution via attacker-controlled email content processed by PEAR email handling before 1.33.0.
Immediate action required
- affected< 1.33.0
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.