CVE-2019-10912

What it is

In Symfony before 2.8.50, 3.x before 3.4.26, 4.x before 4.1.12, and 4.2.x before 4.2.7, it is possible to cache objects that may contain bad user input. On serialization or unserialization, this could result in the deletion of files that the current user has access to. This is related to symfony/cache and symfony/phpunit-bridge.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account. High risk of data tampering.

Exploit odds

2.3% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2019-05-16 22:29 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 02:11 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 2.3% in the next 30 days (EPSS).
• Severity: 7.1 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2019-05-16 22:29 UTC

Last modified

2026-06-17 02:11 UTC

Exploit probability

2.3% · EPSS, next 30 days

Weakness

CWE-502 · Unsafe deserialization

Record status

Modified

Affected

• Sensiolabs Symfony < 2.8.50
• Sensiolabs Symfony < 3.4.26
• Sensiolabs Symfony < 4.1.12
• Sensiolabs Symfony < 4.2.7

Attack profile CVSS 3.0 · 7.1

Attack vector

Network

Complexity

Low

Privileges needed

Low

User interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

High

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2019-10912.md and follow it. Check whether this project is affected by CVE-2019-10912. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge