CVE-2026-25237 PEAR is Vulnerable to PHP Code Execution via preg_replace /e in Bug Update Emails
Critical 9.2
Published
Updated
Check this codebase for CVE-2026-25237 and fix it if it is affected.
What it is: CVE-2026-25237 is a critical vulnerability in pearweb, published on 3 Feb 2026.
Exploitation: There is no known exploitation of CVE-2026-25237 in the wild and no public exploit code.
Affected product: pearweb. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-25237/ (Markdown: https://insights.sbomify.com/CVE-2026-25237/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-25237?
CVE-2026-25237 is a critical vulnerability in pearweb, published on 3 Feb 2026.
Official description
PEAR is a framework and distribution system for reusable PHP components. Prior to version 1.33.0, use of preg_replace() with the /e modifier in bug update email handling can enable PHP code execution if attacker-controlled content reaches the evaluated replacement. This issue has been patched in version 1.33.0.
Weakness: CWE-624
Which versions are affected by CVE-2026-25237?
It affects 1 product.
Products include Pear Pearweb.
How do I fix CVE-2026-25237?
No fix has been published for CVE-2026-25237 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-25237 being exploited?
There is no known exploitation of CVE-2026-25237 in the wild and no public exploit code.
Other vulnerabilities in pearweb
- CVE-2026-25241 PEAR is Vulnerable to SQL Injection in /get/<package>/<version> Endpoint
- CVE-2026-25238 PEAR is Vulnerable to SQL Injection in Bug Subscription Deletion via Weak Email Validation
- CVE-2026-25235 PEAR Has a Predictable Verification Hash in Election Account Requests
- CVE-2026-25239 PEAR is Vulnerable to SQL Injection in apidoc_queue Insert via Unescaped Filename
- CVE-2026-25233 PEAR Has a Roadmap Authorization Bypass via Operator Precedence Bug
Sources
Also known as GHSA-vhw6-hqh9-8r23.