{"vuln_id":"GHSA-h96m-rvf9-jgm2","aliases":["CVE-2025-14178"],"description":"Heap buffer overflow in array_merge()","published_at":"2025-12-18T16:10:32Z","modified_at":"2025-12-19T09:47:08Z","first_seen_at":"2026-11-22T14:05:37.611635Z","severity":"medium","severity_source":"ghsa","cvss_score":6.5,"cvss_vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H","cwe":[],"vendor":null,"product":null,"kev":{"is_kev":false,"date_added":null,"due_date":null,"ransomware":false},"epss":null,"epss_percentile":null,"nvd_status":null,"enriched_at":null,"links":{"nvd":"https://github.com/advisories/GHSA-h96m-rvf9-jgm2"},"matched_alias":null,"items":[{"id":12649,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-h96m-rvf9-jgm2 / CVE-2025-14178: Heap buffer overflow in array_merge()","summary":"Heap buffer overflow in array_merge()\n\nThe following PHP code triggers a reliable heap buffer overflow:\r\n```php\r\n$arr = range(0, 2**29);\r\narray_merge($arr, $arr, $arr, $arr, $arr, $arr, $arr, $arr);\r\n```\r\n\r\nOr the general case:\r\n```php\r\n$power = 24; // You can choose this number 1 <= $power < 32\r\n$arr = range(0, 2**$power);\r\narray_merge(...array_fill(0, 2**(32-$power), $arr));\r\n```\r\n\r\nThis is because packed arrays in array_merge() have an optimization that requires precomputing the count of the elements, done using `count += zend_hash_num_elements(Z_ARRVAL_P(arg));`. However, this may overflow. Note that even if it didn't, it would cause a DoS because array_init() will trigger a bailout with too large counts.\r\n\r\nThe code provided is artificial, but I believe this can happen in the real world with for example large sets of JSON data that are then passed to array_merge(). The total count just has to exceed HT_MAX_SIZE to trigger the DoS or the 32-bit limit to trigger the buffer overflow.\r\n\r\n### Impact\r\n\r\nIf we were using a memory safe language we would \"just\" be limited to the DoS, but now we have heap corruption and all the joys of it.\r\nThis bug has been in PHP since PHP 7.1.\r\n\r\n### Workarounds\r\nPrevent a large number of inputs of long arrays to array_merge().\r\n\r\n### Security impact\r\n\r\nAs noted the example code is just a PoC exploit trigger.\r\n\r\nThe JSON file could be crafted and loaded via json_decode that results in a structure like: [array1, array2, array3, ...]. Then the code could use `array_merge(array1, array2, array3, ...)` from the JSON data. The arrays itself may be relatively small but if the sum of elements exceed the HT_MAX_SIZE bound, the buffer overflow is triggered.\r\n\r\nSomething like this:\r\n\r\n```php\r\n<?php\r\n$array = json_decode(file_get_contents('input.json')); // array of arrays\r\narray_merge(...$array);\r\n```\nPatched:  8.1.34,  8.2.30,  8.3.29,  8.4.16,  8.5.1","url":"https://github.com/php/php-src/security/advisories/GHSA-h96m-rvf9-jgm2","published_at":"2025-12-18T16:10:32Z","updated_at":"2025-12-19T09:47:08Z","fetched_at":"2026-11-22T14:05:37.431187Z","severity":"high","cvss_score":8.2,"epss":0.00455,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"php-src","vuln_id":"CVE-2025-14178","vuln_ids":["CVE-2025-14177","CVE-2025-14178","CVE-2025-14180","GHSA-H96M-RVF9-JGM2"],"tags":["repo-advisory","security","repo:php/php-src","stack"],"cluster_id":11757,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/12649","html":"https://vulnwatch.ve1ve2.com/item/12649"}}]}