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

CVE-2019-10911

HIGHFix: symfony/symfony@a29ce28

CVE-2019-10911 is a high-severity (CVSS 7.5) Improper Authentication vulnerability in symfony/security-http. O3 Security confirms whether CVE-2019-10911 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Improper authentication in Symfony

Also known asGHSA-cchx-mfrc-fwqr
Published
May 16, 2019
Updated
Aug 7, 2026
Affected
15 pkgs
Patched
15 / 15
Exploits
None indexed
Exploitation data as of Aug 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

15 pkgs affected
🐘symfony/security-http🐘symfony/security-http🐘symfony/security-http🐘symfony/security-http🐘symfony/security-http🐘symfony/security🐘symfony/security🐘symfony/security+7 more

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

In Symfony before 2.7.51, 2.8.x before 2.8.50, 3.x before 3.4.26, 4.x before 4.1.12, and 4.2.x before 4.2.7, a vulnerability would allow an attacker to authenticate as a privileged user on sites with user registration and remember me login functionality enabled. This is related to symfony/security.

Affected Packages

15 total 15 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistsymfony/security-http2.7.0&&< 2.7.512.7.51
🐘Packagistsymfony/security-http2.8.0&&< 2.8.502.8.50
🐘Packagistsymfony/security-http3.0.0&&< 3.4.263.4.26
🐘Packagistsymfony/security-http4.0.0&&< 4.1.124.1.12
🐘Packagistsymfony/security-http4.2.0&&< 4.2.74.2.7
🐘Packagistsymfony/security2.7.0&&< 2.7.512.7.51

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/security-http. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update symfony/security-http to 2.7.51 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-10911 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 pinpoints whether CVE-2019-10911 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

Frequently Asked Questions

In Symfony before 2.7.51, 2.8.x before 2.8.50, 3.x before 3.4.26, 4.x before 4.1.12, and 4.2.x before 4.2.7, a vulnerability would allow an attacker to authenticate as a privileged user on sites with user registration and remember me login functionality enabled. This is related to symfony/security.
O3 Security · Impact-Aware SCA

Is CVE-2019-10911 in your dependencies?

O3 detects CVE-2019-10911 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

CVE-2019-10911: Improper authentication in… | O3 Security