Skip to content
major vulnerability· requires attention

Widely used PHP runtime; use-after-free leads to RCE via SOAP; could disrupt many servers.

Web

CVE-2026-6722

9.5
Critical
EPSS 0.89%Patch availableMay 10, 2026

PHP SOAP use-after-free enables remote code execution via crafted SOAP requests.

common questions

Is CVE-2026-6722 being exploited?

Not confirmed. CVE-2026-6722 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.89% probability of exploitation in the next 30 days.

How severe is CVE-2026-6722?

CVE-2026-6722 is rated Critical with a CVSS score of 9.5. 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-6722?

Yes. A fix has been recorded for CVE-2026-6722. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-6722 affect?

CVE-2026-6722 affects PHP 8.2.x < 8.2.31, PHP 8.3.x < 8.3.31, PHP 8.4.x < 8.4.21, PHP 8.5.x < 8.5.6. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-6722?

Upgrade to fixed releases (8.2.31+, 8.3.31+, 8.4.21+, 8.5.6+).

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
PHP 8.2.x < 8.2.31PHP 8.3.x < 8.3.31PHP 8.4.x < 8.4.21PHP 8.5.x < 8.5.6
impact

Remote code execution on affected servers via malicious SOAP requests.

action required

Patch immediately

affected versions
PHP Group PHP
  • affected>= 8.2.* and < 8.2.31
  • affected>= 8.3.* and < 8.3.31
  • affected>= 8.4.* and < 8.4.21
  • affected>= 8.5.* and < 8.5.6

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free