p PatchFirst

PatchFirst · Latest vulnerabilities

symfony/security-http vulnerabilities

Vulnerabilities published for symfony/security-http in the last 30 days: 0. Listed in the KEV catalogue: 0.

RSS ↗
Filter vulnerabilities
Clear filters

Vulnerabilities: 20

  1. CVE-2026-48489

    High · CVSS 8.7EPSS 0.6%Fix available

    Symfony: Security Firewall Bypass via failure_forward Subrequest: Unauthenticated Access to access_control-Protected GET Routes

    Symfony is a PHP framework for web and console applications and a set of reusable PHP components. Prior to 5.4.53, 6.4.41, 7.4.13, and 8.0.13, DefaultAuthenticationFailureHandler honored the request-supplied _failure_path parameter when failure_forward: true was enabled, allowing an unauthenticated failing login request to dispatch a subrequest to access_control-protected GET routes that skipped firewall listeners. This issue is fixed in versions 5.4.53, 6.4.41, 7.4.13, and 8.0.13.

    • Update to 5.4.53
    • Update to 6.4.41
    • Update to 7.4.13
    • Update to 8.0.13
    Published Updated
  2. CVE-2026-45069

    High · CVSS 8.8EPSS 0.26%Fix available

    Symfony: OidcTokenHandler Accepts JWTs Missing aud/iss/exp Claims

    Symfony is a PHP framework for web and console applications and a set of reusable PHP components. Prior to 6.4.40, 7.4.12, and 8.0.12, OidcTokenHandler::verifyClaims() registered audience (aud), issuer (iss), and expiry (exp) checkers but did not pass the mandatory claims list to ClaimCheckerManager::check(), so a validly signed JWT that omitted those claims could pass verification. This issue is fixed in versions 6.4.40, 7.4.12, and 8.0.12.

    • Update to 6.4.40
    • Update to 7.4.12
    • Update to 8.0.12
    Published Updated
  3. CVE-2026-45075

    High · CVSS 8.3EPSS 0.43%Fix available

    Symfony: HEAD Request Bypasses methods: ['GET'] Filter in #[IsGranted] / #[IsSignatureValid] / #[IsCsrfTokenValid]

    Symfony is a PHP framework for web and console applications and a set of reusable PHP components. Prior to 7.4.12 and 8.0.12, method-scoped #[IsGranted], #[IsSignatureValid], and #[IsCsrfTokenValid] attributes can be configured for GET only, but Symfony routes HEAD requests to the GET handler while the attribute check is skipped, allowing protected controllers to execute and leak headers or perform side effects. This issue is fixed in versions 7.4.12 and 8.0.12.

    • Update to 7.4.12
    • Update to 8.0.12
    Published Updated
  4. CVE-2026-45063

    Critical · CVSS 9.1EPSS 0.37%Fix available

    Symfony: Identity Spoofing via Unanchored DN Regex in X509Authenticator

    Symfony is a PHP framework for web and console applications and a set of reusable PHP components. Prior to 5.4.52, 6.4.40, 7.4.12, and 8.0.12, X509Authenticator extracts the user identifier from $_SERVER['SSL_CLIENT_S_DN'] with an unanchored regex that matches emailAddress= anywhere in the distinguished name, allowing an attacker with a trusted certificate containing emailAddress=victim inside another RDN value such as CN to authenticate as the victim. This issue is fixed in versions 5.4.52, 6.4.40, 7.4.12, and 8.0.12.

    • Update to 5.4.52
    • Update to 6.4.40
    • Update to 7.4.12
    • Update to 8.0.12
    Published Updated
  5. CVE-2026-45074

    High · CVSS 7.6EPSS 0.49%Fix available

    Symfony: Cas2Handler Derives CAS service URL from Client Host Header → Cross-Service Ticket Replay

    Symfony is a PHP framework for web and console applications and a set of reusable PHP components. From 7.1.0 until 7.4.12 and 8.0.12, Cas2Handler builds the CAS service parameter from Request::getSchemeAndHttpHost(), which reflects an attacker-controlled Host header when framework.trusted_hosts is not configured; an attacker controlling another application registered with the same CAS server can replay a victim ticket against the Symfony application and authenticate as the victim. This issue is fixed in versions 7.4.12 and 8.0.12.

    • Update to 7.4.12
    • Update to 8.0.12
    Published Updated
  6. CVE-2024-51996

    High · CVSS 7.5EPSS 0.62%Fix available

    Symphony has an Authentication Bypass via RememberMe

    Symphony process is a module for the Symphony PHP framework which executes commands in sub-processes. When consuming a persisted remember-me cookie, Symfony does not check if the username persisted in the database matches the username attached with the cookie, leading to authentication bypass. This vulnerability is fixed in 5.4.47, 6.4.15, and 7.1.8.

    • Update to 5.4.47
    • Update to 6.4.15
    • Update to 7.1.8
    Published Updated
  7. CVE-2023-46733

    Medium · CVSS 6.5EPSS 0.69%Fix available

    Symfony possible session fixation vulnerability

    Symfony is a PHP framework for web and console applications and a set of reusable PHP components. Starting in versions 5.4.21 and 6.2.7 and prior to versions 5.4.31 and 6.3.8, `SessionStrategyListener` does not migrate the session after every successful login. It does so only in case the logged in user changes by means of checking the user identifier. In some use cases, the user identifier doesn't change between the verification phase and the successful login, while the token itself changes from one type (partially-authenticated) to another (fully-authenticated). When this happens, the session id should be regenerated to prevent possible sess

    • Update to 5.4.31
    • Update to 6.3.8
    Published Updated
  8. CVE-2021-32693

    Medium · CVSS 6.8EPSS 1.39%Fix available

    Authentication granted with multiple firewalls

    Symfony is a PHP framework for web and console applications and a set of reusable PHP components. A vulnerability related to firewall authentication is in Symfony starting with version 5.3.0 and prior to 5.3.2. When an application defines multiple firewalls, the token authenticated by one of the firewalls was available for all other firewalls. This could be abused when the application defines different providers for each part of the application, in such a situation, a user authenticated on a part of the application could be considered authenticated on the rest of the application. Starting in version 5.3.2, a patch ensures that the authenticat

    • Update to 5.3.2
    Published Updated
  9. GHSA-g2qj-pmxm-9f8f

    Not ratedFix available

    User enumeration in authentication mechanisms

    Description ----------- The ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user. Resolution ---------- We now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist. The patch for this issue is available [here](https://github.com/symfony/symfony/commit/2a581d22cc621b33d5464ed65c4bc2057f72f011) for branch 3.4. Cred

    • Update to 5.2.8
    Published Updated
  10. CVE-2021-21424

    Medium · CVSS 5.3EPSS 1.64%Fix available

    Prevent user enumeration using Guard or the new Authenticator-based Security

    Symfony is a PHP framework for web and console applications and a set of reusable PHP components. The ability to enumerate users was possible without relevant permissions due to different handling depending on whether the user existed or not when attempting to use the switch users functionality. We now ensure that 403s are returned whether the user exists or not if a user cannot switch to a user or if the user does not exist. The patch for this issue is available for branch 3.4.

    • Update to 5.2.8
    Published Updated
  11. CVE-2020-5275

    High · CVSS 7.6EPSS 1.15%Fix available

    Firewall configured with unanimous strategy was not actually unanimous in symfony/security-http

    In symfony/security-http before versions 4.4.7 and 5.0.7, when a `Firewall` checks access control rule, it iterate overs each rule's attributes and stops as soon as the accessDecisionManager decides to grant access on the attribute, preventing the check of next attributes that should have been take into account in an unanimous strategy. The accessDecisionManager is now called with all attributes at once, allowing the unanimous strategy being applied on each attribute. This issue is patched in versions 4.4.7 and 5.0.7.

    • Update to 4.4.7
    • Update to 5.0.7
    Published Updated
  12. CVE-2019-18886

    Medium · CVSS 5.3EPSS 1.55%Fix available

    CVE-2019-18886

    An issue was discovered in Symfony 4.2.0 to 4.2.11 and 4.3.0 to 4.3.7. The ability to enumerate users was possible due to different handling depending on whether the user existed when making unauthorized attempts to use the switch users functionality. This is related to symfony/security.

    • Update to 4.2.12
    • Update to 4.3.8
    Published Updated
  13. CVE-2019-10911

    High · CVSS 7.5EPSS 1.21%Fix available

    CVE-2019-10911

    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.

    • Update to 2.7.51
    • Update to 2.8.50
    • Update to 3.4.26
    • Update to 4.1.12
    • Update to 4.2.7
    Published Updated
  14. CVE-2018-19790

    Medium · CVSS 6.1EPSS 1.49%Fix available

    CVE-2018-19790

    An open redirect was discovered in Symfony 2.7.x before 2.7.50, 2.8.x before 2.8.49, 3.x before 3.4.20, 4.0.x before 4.0.15, 4.1.x before 4.1.9 and 4.2.x before 4.2.1. By using backslashes in the `_failure_path` input field of login forms, an attacker can work around the redirection target restrictions and effectively redirect the user to any domain after login.

    • Update to 2.7.50
    • Update to 2.8.49
    • Update to 3.4.20
    • Update to 4.0.15
    • Update to 4.1.9
    • Update to 4.2.1
    Published Updated
  15. CVE-2018-11406

    High · CVSS 8.8EPSS 0.75%Fix available

    CVE-2018-11406

    An issue was discovered in the Security component in Symfony 2.7.x before 2.7.48, 2.8.x before 2.8.41, 3.3.x before 3.3.17, 3.4.x before 3.4.11, and 4.0.x before 4.0.11. By default, a user's session is invalidated when the user is logged out. This behavior can be disabled through the invalidate_session option. In this case, CSRF tokens were not erased during logout which allowed for CSRF token fixation.

    • Update to 2.7.48
    • Update to 2.8.41
    • Update to 3.3.17
    • Update to 3.4.11
    • Update to 4.0.11
    Published Updated
  16. CVE-2018-11385

    High · CVSS 8.1EPSS 1.97%Fix available

    CVE-2018-11385

    An issue was discovered in the Security component in Symfony 2.7.x before 2.7.48, 2.8.x before 2.8.41, 3.3.x before 3.3.17, 3.4.x before 3.4.11, and 4.0.x before 4.0.11. A session fixation vulnerability within the "Guard" login feature may allow an attacker to impersonate a victim towards the web application if the session id value was previously known to the attacker.

    • Update to 2.7.48
    • Update to 2.8.41
    • Update to 3.3.17
    • Update to 3.4.11
    • Update to 4.0.11
    Published Updated
  17. CVE-2017-16652

    Medium · CVSS 6.1EPSS 0.77%Fix available

    CVE-2017-16652

    An issue was discovered in Symfony 2.7.x before 2.7.38, 2.8.x before 2.8.31, 3.2.x before 3.2.14, and 3.3.x before 3.3.13. DefaultAuthenticationSuccessHandler or DefaultAuthenticationFailureHandler takes the content of the _target_path parameter and generates a redirect response, but no check is performed on the path, which could be an absolute URL to an external domain. This Open redirect vulnerability can be exploited for example to mount effective phishing attacks.

    • Update to 2.7.38
    • Update to 2.8.31
    • Update to 3.2.14
    • Update to 3.3.13
    Published Updated
  18. CVE-2016-4423

    High · CVSS 7.5EPSS 1.86%Fix available

    CVE-2016-4423

    The attemptAuthentication function in Component/Security/Http/Firewall/UsernamePasswordFormAuthenticationListener.php in Symfony before 2.3.41, 2.7.x before 2.7.13, 2.8.x before 2.8.6, and 3.0.x before 3.0.6 does not limit the length of a username stored in a session, which allows remote attackers to cause a denial of service (session storage consumption) via a series of authentication attempts with long, non-existent usernames.

    • Update to 2.3.41
    • Update to 2.7.13
    • Update to 2.8.6
    • Update to 3.0.6
    Published Updated
  19. CVE-2015-8125

    Not ratedEPSS 2.54%Fix available

    CVE-2015-8125

    Symfony 2.3.x before 2.3.35, 2.6.x before 2.6.12, and 2.7.x before 2.7.7 might allow remote attackers to have unspecified impact via a timing attack involving the (1) Symfony/Component/Security/Http/RememberMe/PersistentTokenBasedRememberMeServices or (2) Symfony/Component/Security/Http/Firewall/DigestAuthenticationListener class in the Symfony Security Component, or (3) legacy CSRF implementation from the Symfony/Component/Form/Extension/Csrf/CsrfProvider/DefaultCsrfProvider class in the Symfony Form component.

    • Update to 2.6.12
    • Update to 2.7.7
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →