Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘 Packagist
Not in CISA KEV

CVE-2013-1397 — symfony/symfony

Fix: symfony/symfony@ba6e315

CVE-2013-1397 is a Code Injection vulnerability in symfony/symfony. A fix is available for symfony/symfony — see the affected versions and patch details below.

Symfony Arbitrary PHP code Execution

Published
May 17, 2022
Updated
Apr 14, 2025
Affected
6 pkgs
Patched
6 / 6
Exploits
None indexed
Exploitation data as of Sep 20, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs75th percentile — riskier than 75% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

6 pkgs affected
🐘symfony/symfony🐘symfony/symfony🐘symfony/symfony🐘symfony/yaml🐘symfony/yaml🐘symfony/yaml

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Symfony 2.0.x before 2.0.22, 2.1.x before 2.1.7, and 2.2.x remote attackers to execute arbitrary PHP code via a serialized PHP object to the (1) Yaml::parse or (2) Yaml\Parser::parse function, a different vulnerability than CVE-2013-1348.

Affected Packages

6 total 6 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistsymfony/symfony≥ 2.2.0-BETA1&&< 2.2.0-BETA22.2.0-BETA2composer require symfony/symfony:^2.2.0-BETA2
🐘Packagistsymfony/symfony≥ 2.0.0&&< 2.0.222.0.22composer require symfony/symfony:^2.0.22
🐘Packagistsymfony/symfony≥ 2.1.0&&< 2.1.72.1.7composer require symfony/symfony:^2.1.7
🐘Packagistsymfony/yaml≥ 2.0.0&&< 2.0.222.0.22composer require symfony/yaml:^2.0.22
🐘Packagistsymfony/yaml≥ 2.1.0&&< 2.1.72.1.7composer require symfony/yaml:^2.1.7
🐘Packagistsymfony/yaml≥ 2.2.0-BETA1&&< 2.2.0-BETA22.2.0-BETA2composer require symfony/yaml:^2.2.0-BETA2

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for symfony/symfony, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update symfony/symfony to 2.2.0-BETA2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-1397 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2013-1397 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2013-1397. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Symfony 2.0.x before 2.0.22, 2.1.x before 2.1.7, and 2.2.x remote attackers to execute arbitrary PHP code via a serialized PHP object to the (1) Yaml::parse or (2) Yaml\Parser::parse function, a different vulnerability than CVE-2013-1348.
O3 Security · Impact-Aware SCA

Is CVE-2013-1397 in your dependencies?

O3 Security finds CVE-2013-1397 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works
CVE-2013-1397: symfony/symfony | O3 Security