Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-17544: Out-of-bounds write in PHP BCMath bccomp()

Published Jul 30, 2026 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.1High · v4
EPSS0.42%37th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
PHP Group
IdentifiersCVE-2026-17544CWE-787 · Out-of-bounds Write

CVE-2026-17544 is an out-of-bounds write vulnerability in PHP's BCMath extension affecting PHP 8.4.x before 8.4.24 and 8.5.x before 8.5.9. When bccomp() processes attacker-controlled numeric strings with a specific scale value, bc_str2num() can truncate fractional digits and remove trailing zeroes, reducing the allocated buffer size without updating the endpoint of the fractional data being copied. The resulting out-of-bounds write can corrupt stack or heap memory, causing crashes and potentially arbitrary code execution.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Exploitation can corrupt stack or heap memory and cause denial of service through PHP crashes. Arbitrary code execution is also possible, with exploitability depending on application conditions and the runtime environment. Remote, unauthenticated exploitation is reported for affected Oracle Communications Unified Assurance deployments.

Mitigation

If you can’t patch tonight, do this now.

No vulnerability-specific vendor workaround is established. Until updates are installed, limit exposure of PHP applications to untrusted input, restrict access to affected application interfaces, and apply least-privilege controls to PHP service accounts. These measures reduce exposure but do not correct the memory-corruption defect.

Remediation

Patch, then assume compromise.

Upgrade PHP 8.4.x to 8.4.24 or later, or PHP 8.5.x to 8.5.9 or later. The fix updates the fractional endpoint after zero truncation so copied data fits the allocated buffer. For distribution packages, install the vendor-patched release: Ubuntu 26.04 LTS PHP 8.5.4-0ubuntu1.3, Debian trixie php8.4 8.4.24-1~deb13u1 or later, or the Red Hat Enterprise Linux 10.2 updates covered by RHSA-2026:56969. Applicable Tanzu deployments can use PHP Buildpack 4.6.82, which explicitly includes the fix. Affected Oracle Communications deployments should apply the relevant September 2026 Critical Patch Update.

Public exploits

Exploits

1 exploit validated by Mallory's analysis. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
CVE-2026-17544This repository is a compact exploit repo containing one real exploit file, exploit.php, plus a README and .gitignore. The exploit is a standalone PHP proof-of-concept/operational exploit for CVE-2026-17544, described as an out-of-bounds zero-write in PHP's rewritten bcmath implementation (bc_str2num) affecting PHP 8.4.x and 8.5.x in the vulnerable ranges. It is not a scanner or detector; it performs active exploitation. Repository structure: README.md explains the vulnerability, threat model, affected versions, usage, and exploitation stages. exploit.php contains the full exploit logic for both CLI and web contexts. There are no auxiliary modules, no framework metadata, and no external dependencies beyond a vulnerable PHP runtime with bcmath enabled. Main exploit capability: the code turns a bcmath-triggered OOB zero-write into a refcount-desynchronization/use-after-free condition on a neighboring zend_string, then uses that to obtain a giant-string relative read/write primitive. From there it builds a fault-safe arbitrary read primitive, leaks a text pointer, scans memory downward page-by-page to find the ELF base of the mapped PHP binary, parses ELF program headers to locate the writable .data segment, scans .data for the shell_exec zend_function_entry, resolves the zif_shell_exec handler address at runtime, and finally constructs fake Zend class/function/hash-table structures in writable memory to invoke that handler through a forged method call. The result is memory-only command execution with returned output, explicitly intended to bypass disable_functions and open_basedir. Operational flow in exploit.php: it sprays strings, frees a hole, triggers bccomp() with a crafted numeric string to induce the OOB write, validates giant-string corruption, creates Probe objects to locate controllable object memory, rewires a property into a fake zend_reference for arbitrary reads, leaks handler/text/base/data addresses, finds shell_exec, builds fake zend_string/zend_function/bucket/class_entry structures inside a controlled buffer, corrupts an object's class pointer to the fake class, invokes a fake method name (pwn) with attacker-controlled command input, restores the original class pointer, and echoes the command output. Attack surface and delivery: the exploit supports local CLI execution (`php exploit.php "id; uname -a"`) and web-based post-exploitation by deploying the script as a PHP file and passing a cmd parameter via GET or POST. It does not target a remote network service directly by IP/domain; instead it assumes the attacker already has the ability to execute PHP code in the target environment. The README explicitly states this is a sandbox escape/post-exploitation primitive rather than input-only remote RCE. In a pure user-input-to-bcmath scenario, the claimed impact is denial of service rather than full code execution. Notable fingerprintable observables include the use of the cmd request parameter, CLI argument $argv[1], the vulnerable bccomp() trigger, the fake method name pwn, and the runtime search for shell_exec/zif_shell_exec inside the PHP process image. No hardcoded external C2, URLs, IPs, or domains are present. The exploit is self-contained and performs all resolution in-process at runtime.r2qa · Disclosed Aug 15, 2026 · php · markdown · local · webPoC
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
PHP GroupPhpapplication
FAQ

Frequently asked questions

Is CVE-2026-17544 exploited in the wild?
As of Oct 8, 2026, Mallory has no reports of CVE-2026-17544 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-17544?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-17544, the earliest disclosed Aug 15, 2026.
Is there a patch for CVE-2026-17544?
Upgrade PHP 8.4.x to 8.4.24 or later, or PHP 8.5.x to 8.5.9 or later. The fix updates the fractional endpoint after zero truncation so copied data fits the allocated buffer.
What products are affected by CVE-2026-17544?
PHP Group Php.
How severe is CVE-2026-17544?
CVE-2026-17544 has a CVSS v4 score of 8.1 (High) and an EPSS score of 0.42% (37th percentile) as of Oct 8, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity6Community discussion across Reddit, Mastodon, and other social sources.