CVE-2025-14178 [Medium] | Integer Overflow in Php

In PHP versions:8.1.* before 8.1.34, 8.2.* before 8.2.30, 8.3.* before 8.3.29, 8.4.* before 8.4.16, 8.5.* before 8.5.1, a heap buffer overflow occurs in array_merge() when the total element count of packed arrays exceeds 32-bit limits or HT_MAX_SIZE, due to an integer overflow in the precomputation of element counts using zend_hash_num_elements(). This may lead to memory corruption or crashes and affect the integrity and availability of the target server.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-02-18	0.05%	0.02%	-0.03%
2	2026-01-02	0.04%	0.05%	+0.01%
3	2025-12-28	—	0.04%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-02-18

0.05%

0.02%

-0.03%

2026-01-02

0.04%

0.05%

+0.01%

2025-12-28

—

0.04%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
6.5	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	2.2	4.2	[email protected]
8.2	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	3.9	4.2	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

6.5

3.1

MEDIUM

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

2.2

4.2

[email protected]

8.2

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

3.9

4.2

[email protected]

OS Trackers for CVE-2025-14178

vendor	priority	summary	link
`alpine`	—	CVE-2025-14178: 4 source package rows (php82, php83, php84, php85); 9 state rows across 3 repos (3.22-community, 3.23-community, edge-community); fixed 9, open 0.	https://security.alpinelinux.org/vuln/CVE-2025-14178
`debian`	not yet assigned	CVE-2025-14178 not yet assigned priority: Debian including 3 source packages (php7.4, php8.2, php8.4), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2025-14178
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2025-14178
`suse`	medium	CVE-2025-14178 severity moderate: SUSE including 393 source package names (2.2.1-7.2:libpython3_11-1_0-3.11.13-slfo.1.1_1.1, 2.2.1-7.2:python311-3.11.13-slfo.1.1_1.1, …), 1141 product×package rows across 45 product lines (Container suse/sl-micro/6.0/toolbox, Container suse/sl-micro/6.1/baremetal-os-container, … (45 product lines)): Fixed 1087, First Fixed 53, Known Not Affected 1.	https://www.suse.com/security/cve/CVE-2025-14178/
`ubuntu`	medium	CVE-2025-14178 medium priority: Ubuntu including 7 source packages (php5, php7.0, …), 39 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): DNE 24, needs-triage 7, released 6, not-affected 2.	https://ubuntu.com/security/CVE-2025-14178

Affected software / configurations for CVE-2025-14178

Vendor	Product	Version	Raw CPE
php	php	>= 8.1.0, < 8.1.34	cpe:2.3:a:php:php::::::::
php	php	>= 8.2.0, < 8.2.30	cpe:2.3:a:php:php::::::::
php	php	>= 8.3.0, < 8.3.29	cpe:2.3:a:php:php::::::::
php	php	>= 8.4.0, < 8.4.16	cpe:2.3:a:php:php::::::::
php	php	>= 8.5.0, < 8.5.1	cpe:2.3:a:php:php::::::::

References for CVE-2025-14178

URL	Tags
https://github.com/php/php-src/security/advisories/GHSA-h96m-rvf9-jgm2	Vendor Advisory
https://lists.debian.org/debian-lts-announce/2026/01/msg00019.html

URL

CVE-2025-14178 | Heap buffer overflow in array_merge()

Exploit prediction scoring system (EPSS) score for CVE-2025-14178

Common vulnerability scoring system (CVSS) metrics for CVE-2025-14178

Weakness enumeration for CVE-2025-14178

OS Trackers for CVE-2025-14178

Affected software / configurations for CVE-2025-14178

References for CVE-2025-14178