PHP up to 8.2.35/8.3.36/8.4.27/8.5.12 Session Serializer input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00+ |
Summary
A vulnerability was found in PHP up to 8.2.35/8.3.36/8.4.27/8.5.12. It has been classified as critical. This issue affects some unknown processing of the component Session Serializer. Performing a manipulation results in input validation. This vulnerability is known as CVE-2026-115560. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is recommended.
Details
A vulnerability classified as critical has been found in PHP up to 8.2.35/8.3.36/8.4.27/8.5.12. This affects an unknown code block of the component Session Serializer. The manipulation with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Session serializer mismatch can lead to remote code execution. Session upload progress, when enabled, can store attacker-controlled data in a session key using the php_binary or php_serialize session serializer. If the same session is later read with the php serializer, because session.serialize_handler is changed at runtime or differs between applications sharing a session store, bytes inside the key can be passed to the unserializer. A remote attacker able to submit a multipart upload can inject objects, which may lead to code execution when the reading application contains a suitable gadget chain, or to session corruption or denial of service. This issue affects PHP versions 8.2.* before 8.2.36, 8.3.* before 8.3.37, 8.4.* before 8.4.28 and 8.5.* before 8.5.13.
It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-115560 since 10/23/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 11/19/2026).
Upgrading to version 8.2.36, 8.3.37, 8.4.28 or 8.5.13 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
- 8.2.0
- 8.2.1
- 8.2.2
- 8.2.3
- 8.2.4
- 8.2.5
- 8.2.6
- 8.2.7
- 8.2.8
- 8.2.9
- 8.2.10
- 8.2.11
- 8.2.12
- 8.2.13
- 8.2.14
- 8.2.15
- 8.2.16
- 8.2.17
- 8.2.18
- 8.2.19
- 8.2.20
- 8.2.21
- 8.2.22
- 8.2.23
- 8.2.24
- 8.2.25
- 8.2.26
- 8.2.27
- 8.2.28
- 8.2.29
- 8.2.30
- 8.2.31
- 8.2.32
- 8.2.33
- 8.2.34
- 8.2.35
- 8.3.0
- 8.3.1
- 8.3.2
- 8.3.3
- 8.3.4
- 8.3.5
- 8.3.6
- 8.3.7
- 8.3.8
- 8.3.9
- 8.3.10
- 8.3.11
- 8.3.12
- 8.3.13
- 8.3.14
- 8.3.15
- 8.3.16
- 8.3.17
- 8.3.18
- 8.3.19
- 8.3.20
- 8.3.21
- 8.3.22
- 8.3.23
- 8.3.24
- 8.3.25
- 8.3.26
- 8.3.27
- 8.3.28
- 8.3.29
- 8.3.30
- 8.3.31
- 8.3.32
- 8.3.33
- 8.3.34
- 8.3.35
- 8.3.36
- 8.4.0
- 8.4.1
- 8.4.2
- 8.4.3
- 8.4.4
- 8.4.5
- 8.4.6
- 8.4.7
- 8.4.8
- 8.4.9
- 8.4.10
- 8.4.11
- 8.4.12
- 8.4.13
- 8.4.14
- 8.4.15
- 8.4.16
- 8.4.17
- 8.4.18
- 8.4.19
- 8.4.20
- 8.4.21
- 8.4.22
- 8.4.23
- 8.4.24
- 8.4.25
- 8.4.26
- 8.4.27
- 8.5.0
- 8.5.1
- 8.5.2
- 8.5.3
- 8.5.4
- 8.5.5
- 8.5.6
- 8.5.7
- 8.5.8
- 8.5.9
- 8.5.10
- 8.5.11
- 8.5.12
License
Website
- Product: https://www.php.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Input validationCWE: CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: PHP 8.2.36/8.3.37/8.4.28/8.5.13
Timeline
10/23/2026 CVE reserved11/19/2026 Advisory disclosed
11/19/2026 VulDB entry created
11/19/2026 VulDB entry last update
Sources
Product: php.orgAdvisory: github.com
Status: Confirmed
CNA: php
CVE: CVE-2026-115560 (🔒)
GCVE (CVE): GCVE-0-2026-115560
GCVE (VulDB): GCVE-100-440235
Entry
Created: 11/19/2026 16:01Changes: 11/19/2026 16:01 (67)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.