Vulnerability-Lookup

CVE-2026-123746 (GCVE-0-2026-123746)

Vulnerability from cvelistv5 – Published: 2026-11-06 12:36 – Updated: 2026-11-06 12:36

Title

Symfony: Programmatic Logins Skip the checkPostAuth() Method of User Checkers

Summary

The Symfony Security HTTP component AuthenticatorManager::authenticateUser() does not run the firewall user checker’s checkPostAuth() method when a user is authenticated programmatically, allowing an account rejected by a custom user checker, such as an expired account, to be authenticated in Symfony versions prior to 5.4.56, 6.x prior to 6.4.50, 7.x prior to 7.4.23, and 8.x prior to 8.1.11. AuthenticatorManager::authenticateUser() is used by UserAuthenticatorInterface::authenticateUser() and by the SecurityBundle’s Security::login() to authenticate a user programmatically, but it does not dispatch the security.authentication.success event, on which checkPostAuth() runs. The fix for CVE-2024-50341 made Security::login() call checkPreAuth(), but checkPostAuth() was still skipped. As a result, an account rejected by a custom user checker in checkPostAuth() is refused by form login and the other authenticators of the firewall, but can still be authenticated programmatically. Applications are affected when they use a custom user checker that rejects users in checkPostAuth() and authenticate users programmatically, for example after a password reset or an e-mail verification link. A user whose account is rejected can then obtain an authenticated session through that flow. The default user checker does nothing in checkPostAuth(), so the default configuration is not affected. The fix makes AuthenticatorManager::authenticateUser() dispatch the security.authentication.success event once the token is created and before it is stored, as authentications through the firewall do, so that checkPostAuth() runs and can reject the user.

Severity

2.3 (Low)


                        
                          CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

CWE

CWE-288 - Authentication bypass using an alternate path or channel

Assigner

Checkmarx CNA under the mitre root

CNA scorecard B 88/100 over 23 records in the last 180 days details

References

2 references

URL	Tags
https://github.com/symfony/symfony/security/advis…	third-party-advisory
https://github.com/symfony/symfony/commit/af0aae5…	patch

Impacted products

1 product

Vendor	Product	Version	CPE status
sensiolabs	symfony	Affected: 0 , < 5.4.56 (git) Affected: 6.0.0 , < 6.4.50 (git) Affected: 7.0.0 , < 7.4.23 (git) Affected: 8.0.0 , < 8.1.11 (git) cpe:2.3:a:sensiolabs:symfony:::::::: cpe:2.3:a:sensiolabs:symfony:::::::: cpe:2.3:a:sensiolabs:symfony:::::::: cpe:2.3:a:sensiolabs:symfony::::::::

Credits

Nicolas Grekas Vincent Cassiau from CyberVanguard

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "collectionURL": "https://packagist.org/packages/symfony/security-http",
          "defaultStatus": "unaffected",
          "modules": [
            "Symfony\\Component\\Security\\Http\\Authentication\\AuthenticatorManager"
          ],
          "packageName": "symfony/security-http",
          "product": "symfony",
          "repo": "https://github.com/symfony/security-http",
          "vendor": "sensiolabs",
          "versions": [
            {
              "lessThan": "5.4.56",
              "status": "affected",
              "version": "0",
              "versionType": "git"
            },
            {
              "lessThan": "6.4.50",
              "status": "affected",
              "version": "6.0.0",
              "versionType": "git"
            },
            {
              "lessThan": "7.4.23",
              "status": "affected",
              "version": "7.0.0",
              "versionType": "git"
            },
            {
              "lessThan": "8.1.11",
              "status": "affected",
              "version": "8.0.0",
              "versionType": "git"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:sensiolabs:symfony:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.4.56",
                  "versionStartIncluding": "0",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:a:sensiolabs:symfony:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.4.50",
                  "versionStartIncluding": "6.0.0",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:a:sensiolabs:symfony:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.4.23",
                  "versionStartIncluding": "7.0.0",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:a:sensiolabs:symfony:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "8.1.11",
                  "versionStartIncluding": "8.0.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ],
          "operator": "OR"
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "Nicolas Grekas"
        },
        {
          "lang": "en",
          "type": "reporter",
          "value": "Vincent Cassiau from CyberVanguard"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003e\u003cspan\u003eThe Symfony Security HTTP component\u0026nbsp;\u003c/span\u003e\u003ccode\u003eAuthenticatorManager::authenticateUser()\u003c/code\u003e\u003cspan\u003e does not run the firewall user checker\u2019s \u003c/span\u003e\u003ccode\u003echeckPostAuth()\u003c/code\u003e\u003cspan\u003e method when a user is authenticated programmatically, allowing an account rejected by a custom user checker, such as an expired account, to be authenticated in\u003c/span\u003e\u0026nbsp;Symfony versions prior to 5.4.56, 6.x prior to 6.4.50, 7.x prior to 7.4.23, and 8.x prior to 8.1.11.\u003c/p\u003e\u003cp\u003e\u003ccode\u003eAuthenticatorManager::authenticateUser()\u003c/code\u003e is used by \u003ccode\u003eUserAuthenticatorInterface::authenticateUser()\u003c/code\u003e and by the SecurityBundle\u2019s \u003ccode\u003eSecurity::login()\u003c/code\u003e to authenticate a user programmatically, but it\u0026nbsp;does not dispatch the \u003ccode\u003esecurity.authentication.success\u003c/code\u003e event, on which \u003ccode\u003echeckPostAuth()\u003c/code\u003e runs.\u0026nbsp;\u003cspan\u003eThe fix for CVE-2024-50341 made \u003c/span\u003e\u003ccode\u003eSecurity::login()\u003c/code\u003e\u003cspan\u003e call \u003c/span\u003e\u003ccode\u003echeckPreAuth()\u003c/code\u003e\u003cspan\u003e, but \u003c/span\u003e\u003ccode\u003echeckPostAuth()\u003c/code\u003e\u003cspan\u003e was still skipped. As a result, an account rejected by a custom user checker in \u003c/span\u003e\u003ccode\u003echeckPostAuth()\u003c/code\u003e\u003cspan\u003e\u0026nbsp;is refused by form login and the other authenticators of the firewall, but can still be authenticated programmatically.\u003c/span\u003e\u003c/p\u003e\u003cp\u003e\u003cspan\u003eApplications are affected when they use a custom user checker that rejects users in \u003c/span\u003e\u003ccode\u003echeckPostAuth()\u003c/code\u003e\u003cspan\u003e and authenticate users programmatically, for example after a password reset or an e-mail verification link.\u0026nbsp;\u003c/span\u003eA user whose account is rejected can then obtain an authenticated session through that flow\u003cspan\u003e. The default user checker does nothing in \u003c/span\u003e\u003ccode\u003echeckPostAuth()\u003c/code\u003e\u003cspan\u003e, so the default configuration is not affected.\u003c/span\u003e\u003c/p\u003e\u003cp\u003eThe fix makes\u0026nbsp;\u003ccode\u003eAuthenticatorManager::authenticateUser()\u003c/code\u003e\u0026nbsp;dispatch the \u003ccode\u003esecurity.authentication.success\u003c/code\u003e event once the token is created and before it is stored, as authentications through the firewall do, so that \u003ccode\u003echeckPostAuth()\u003c/code\u003e runs and can reject the user.\u003c/p\u003e"
            }
          ],
          "value": "The Symfony Security HTTP component\u00a0AuthenticatorManager::authenticateUser() does not run the firewall user checker\u2019s checkPostAuth() method when a user is authenticated programmatically, allowing an account rejected by a custom user checker, such as an expired account, to be authenticated in\u00a0Symfony versions prior to 5.4.56, 6.x prior to 6.4.50, 7.x prior to 7.4.23, and 8.x prior to 8.1.11.\n\n\n\nAuthenticatorManager::authenticateUser() is used by UserAuthenticatorInterface::authenticateUser() and by the SecurityBundle\u2019s Security::login() to authenticate a user programmatically, but it\u00a0does not dispatch the security.authentication.success event, on which checkPostAuth() runs.\u00a0The fix for CVE-2024-50341 made Security::login() call checkPreAuth(), but checkPostAuth() was still skipped. As a result, an account rejected by a custom user checker in checkPostAuth()\u00a0is refused by form login and the other authenticators of the firewall, but can still be authenticated programmatically.\n\n\n\nApplications are affected when they use a custom user checker that rejects users in checkPostAuth() and authenticate users programmatically, for example after a password reset or an e-mail verification link.\u00a0A user whose account is rejected can then obtain an authenticated session through that flow. The default user checker does nothing in checkPostAuth(), so the default configuration is not affected.\n\n\n\nThe fix makes\u00a0AuthenticatorManager::authenticateUser()\u00a0dispatch the security.authentication.success event once the token is created and before it is stored, as authentications through the firewall do, so that checkPostAuth() runs and can reject the user."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "Automatable": "NOT_DEFINED",
            "Recovery": "NOT_DEFINED",
            "Safety": "NOT_DEFINED",
            "attackComplexity": "LOW",
            "attackRequirements": "PRESENT",
            "attackVector": "NETWORK",
            "baseScore": 2.3,
            "baseSeverity": "LOW",
            "exploitMaturity": "NOT_DEFINED",
            "privilegesRequired": "LOW",
            "providerUrgency": "NOT_DEFINED",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "valueDensity": "NOT_DEFINED",
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "LOW",
            "vulnIntegrityImpact": "LOW",
            "vulnerabilityResponseEffort": "NOT_DEFINED"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-288",
              "description": "CWE-288 Authentication bypass using an alternate path or channel",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-06T12:36:50.994Z",
        "orgId": "596c5446-0ce5-4ba2-aa66-48b3b757a647",
        "shortName": "Checkmarx"
      },
      "references": [
        {
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://github.com/symfony/symfony/security/advisories/GHSA-8f57-m8wj-x65w"
        },
        {
          "tags": [
            "patch"
          ],
          "url": "https://github.com/symfony/symfony/commit/af0aae5012beedf0a0c3fd581fd8b9ef696240c4"
        }
      ],
      "source": {
        "advisory": "GHSA-8f57-m8wj-x65w",
        "discovery": "UNKNOWN"
      },
      "title": "Symfony: Programmatic Logins Skip the checkPostAuth() Method of User Checkers",
      "x_generator": {
        "engine": "Vulnogram 1.0.5"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "596c5446-0ce5-4ba2-aa66-48b3b757a647",
    "assignerShortName": "Checkmarx",
    "cveId": "CVE-2026-123746",
    "datePublished": "2026-11-06T12:36:50.994Z",
    "dateReserved": "2026-11-06T12:28:14.998Z",
    "dateUpdated": "2026-11-06T12:36:50.994Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-123746",
      "date": "2026-11-07",
      "epss": "0.00279",
      "percentile": "0.20452"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "collectionURL": "https://packagist.org/packages/symfony/security-http",
                "defaultStatus": "unaffected",
                "modules": [
                  "Symfony\\Component\\Security\\Http\\Authentication\\AuthenticatorManager"
                ],
                "packageName": "symfony/security-http",
                "product": "symfony",
                "repo": "https://github.com/symfony/security-http",
                "vendor": "sensiolabs",
                "versions": [
                  {
                    "lessThan": "5.4.56",
                    "status": "affected",
                    "version": "0",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "6.4.50",
                    "status": "affected",
                    "version": "6.0.0",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "7.4.23",
                    "status": "affected",
                    "version": "7.0.0",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "8.1.11",
                    "status": "affected",
                    "version": "8.0.0",
                    "versionType": "git"
                  }
                ]
              }
            ],
            "source": "596c5446-0ce5-4ba2-aa66-48b3b757a647"
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "The Symfony Security HTTP component\u00a0AuthenticatorManager::authenticateUser() does not run the firewall user checker\u2019s checkPostAuth() method when a user is authenticated programmatically, allowing an account rejected by a custom user checker, such as an expired account, to be authenticated in\u00a0Symfony versions prior to 5.4.56, 6.x prior to 6.4.50, 7.x prior to 7.4.23, and 8.x prior to 8.1.11.\n\n\n\nAuthenticatorManager::authenticateUser() is used by UserAuthenticatorInterface::authenticateUser() and by the SecurityBundle\u2019s Security::login() to authenticate a user programmatically, but it\u00a0does not dispatch the security.authentication.success event, on which checkPostAuth() runs.\u00a0The fix for CVE-2024-50341 made Security::login() call checkPreAuth(), but checkPostAuth() was still skipped. As a result, an account rejected by a custom user checker in checkPostAuth()\u00a0is refused by form login and the other authenticators of the firewall, but can still be authenticated programmatically.\n\n\n\nApplications are affected when they use a custom user checker that rejects users in checkPostAuth() and authenticate users programmatically, for example after a password reset or an e-mail verification link.\u00a0A user whose account is rejected can then obtain an authenticated session through that flow. The default user checker does nothing in checkPostAuth(), so the default configuration is not affected.\n\n\n\nThe fix makes\u00a0AuthenticatorManager::authenticateUser()\u00a0dispatch the security.authentication.success event once the token is created and before it is stored, as authentications through the firewall do, so that checkPostAuth() runs and can reject the user."
          }
        ],
        "id": "CVE-2026-123746",
        "lastModified": "2026-11-06T21:40:43.450",
        "metrics": {
          "cvssMetricV40": [
            {
              "cvssData": {
                "Automatable": "NOT_DEFINED",
                "Recovery": "NOT_DEFINED",
                "Safety": "NOT_DEFINED",
                "attackComplexity": "LOW",
                "attackRequirements": "PRESENT",
                "attackVector": "NETWORK",
                "availabilityRequirement": "NOT_DEFINED",
                "baseScore": 2.3,
                "baseSeverity": "LOW",
                "confidentialityRequirement": "NOT_DEFINED",
                "exploitMaturity": "NOT_DEFINED",
                "integrityRequirement": "NOT_DEFINED",
                "modifiedAttackComplexity": "NOT_DEFINED",
                "modifiedAttackRequirements": "NOT_DEFINED",
                "modifiedAttackVector": "NOT_DEFINED",
                "modifiedPrivilegesRequired": "NOT_DEFINED",
                "modifiedSubAvailabilityImpact": "NOT_DEFINED",
                "modifiedSubConfidentialityImpact": "NOT_DEFINED",
                "modifiedSubIntegrityImpact": "NOT_DEFINED",
                "modifiedUserInteraction": "NOT_DEFINED",
                "modifiedVulnAvailabilityImpact": "NOT_DEFINED",
                "modifiedVulnConfidentialityImpact": "NOT_DEFINED",
                "modifiedVulnIntegrityImpact": "NOT_DEFINED",
                "privilegesRequired": "LOW",
                "providerUrgency": "NOT_DEFINED",
                "subAvailabilityImpact": "NONE",
                "subConfidentialityImpact": "NONE",
                "subIntegrityImpact": "NONE",
                "userInteraction": "NONE",
                "valueDensity": "NOT_DEFINED",
                "vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
                "version": "4.0",
                "vulnAvailabilityImpact": "NONE",
                "vulnConfidentialityImpact": "LOW",
                "vulnIntegrityImpact": "LOW",
                "vulnerabilityResponseEffort": "NOT_DEFINED"
              },
              "source": "596c5446-0ce5-4ba2-aa66-48b3b757a647",
              "type": "Secondary"
            }
          ]
        },
        "published": "2026-11-06T13:17:29.950",
        "references": [
          {
            "source": "596c5446-0ce5-4ba2-aa66-48b3b757a647",
            "url": "https://github.com/symfony/symfony/commit/af0aae5012beedf0a0c3fd581fd8b9ef696240c4"
          },
          {
            "source": "596c5446-0ce5-4ba2-aa66-48b3b757a647",
            "url": "https://github.com/symfony/symfony/security/advisories/GHSA-8f57-m8wj-x65w"
          }
        ],
        "sourceIdentifier": "596c5446-0ce5-4ba2-aa66-48b3b757a647",
        "vulnStatus": "Awaiting Analysis",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-288"
              }
            ],
            "source": "596c5446-0ce5-4ba2-aa66-48b3b757a647",
            "type": "Secondary"
          }
        ]
      }
    }
  }
}

FKIE_CVE-2026-123746

Vulnerability from fkie_nvd - Published: 2026-11-06 13:17 - Updated: 2026-11-06 21:40

Severity

2.3 (Low) - CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Summary

References

	URL	Tags
	596c5446-0ce5-4ba2-aa66-48b3b757a647	https://github.com/symfony/symfony/commit/af0aae5012beedf0a0c3fd581fd8b9ef696240c4
	596c5446-0ce5-4ba2-aa66-48b3b757a647	https://github.com/symfony/symfony/security/advisories/GHSA-8f57-m8wj-x65w

Impacted products

	Vendor	Product	Version

JSON

To clipboard

{
  "affected": [
    {
      "affectedData": [
        {
          "collectionURL": "https://packagist.org/packages/symfony/security-http",
          "defaultStatus": "unaffected",
          "modules": [
            "Symfony\\Component\\Security\\Http\\Authentication\\AuthenticatorManager"
          ],
          "packageName": "symfony/security-http",
          "product": "symfony",
          "repo": "https://github.com/symfony/security-http",
          "vendor": "sensiolabs",
          "versions": [
            {
              "lessThan": "5.4.56",
              "status": "affected",
              "version": "0",
              "versionType": "git"
            },
            {
              "lessThan": "6.4.50",
              "status": "affected",
              "version": "6.0.0",
              "versionType": "git"
            },
            {
              "lessThan": "7.4.23",
              "status": "affected",
              "version": "7.0.0",
              "versionType": "git"
            },
            {
              "lessThan": "8.1.11",
              "status": "affected",
              "version": "8.0.0",
              "versionType": "git"
            }
          ]
        }
      ],
      "source": "596c5446-0ce5-4ba2-aa66-48b3b757a647"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "The Symfony Security HTTP component\u00a0AuthenticatorManager::authenticateUser() does not run the firewall user checker\u2019s checkPostAuth() method when a user is authenticated programmatically, allowing an account rejected by a custom user checker, such as an expired account, to be authenticated in\u00a0Symfony versions prior to 5.4.56, 6.x prior to 6.4.50, 7.x prior to 7.4.23, and 8.x prior to 8.1.11.\n\n\n\nAuthenticatorManager::authenticateUser() is used by UserAuthenticatorInterface::authenticateUser() and by the SecurityBundle\u2019s Security::login() to authenticate a user programmatically, but it\u00a0does not dispatch the security.authentication.success event, on which checkPostAuth() runs.\u00a0The fix for CVE-2024-50341 made Security::login() call checkPreAuth(), but checkPostAuth() was still skipped. As a result, an account rejected by a custom user checker in checkPostAuth()\u00a0is refused by form login and the other authenticators of the firewall, but can still be authenticated programmatically.\n\n\n\nApplications are affected when they use a custom user checker that rejects users in checkPostAuth() and authenticate users programmatically, for example after a password reset or an e-mail verification link.\u00a0A user whose account is rejected can then obtain an authenticated session through that flow. The default user checker does nothing in checkPostAuth(), so the default configuration is not affected.\n\n\n\nThe fix makes\u00a0AuthenticatorManager::authenticateUser()\u00a0dispatch the security.authentication.success event once the token is created and before it is stored, as authentications through the firewall do, so that checkPostAuth() runs and can reject the user."
    }
  ],
  "id": "CVE-2026-123746",
  "lastModified": "2026-11-06T21:40:43.450",
  "metrics": {
    "cvssMetricV40": [
      {
        "cvssData": {
          "Automatable": "NOT_DEFINED",
          "Recovery": "NOT_DEFINED",
          "Safety": "NOT_DEFINED",
          "attackComplexity": "LOW",
          "attackRequirements": "PRESENT",
          "attackVector": "NETWORK",
          "availabilityRequirement": "NOT_DEFINED",
          "baseScore": 2.3,
          "baseSeverity": "LOW",
          "confidentialityRequirement": "NOT_DEFINED",
          "exploitMaturity": "NOT_DEFINED",
          "integrityRequirement": "NOT_DEFINED",
          "modifiedAttackComplexity": "NOT_DEFINED",
          "modifiedAttackRequirements": "NOT_DEFINED",
          "modifiedAttackVector": "NOT_DEFINED",
          "modifiedPrivilegesRequired": "NOT_DEFINED",
          "modifiedSubAvailabilityImpact": "NOT_DEFINED",
          "modifiedSubConfidentialityImpact": "NOT_DEFINED",
          "modifiedSubIntegrityImpact": "NOT_DEFINED",
          "modifiedUserInteraction": "NOT_DEFINED",
          "modifiedVulnAvailabilityImpact": "NOT_DEFINED",
          "modifiedVulnConfidentialityImpact": "NOT_DEFINED",
          "modifiedVulnIntegrityImpact": "NOT_DEFINED",
          "privilegesRequired": "LOW",
          "providerUrgency": "NOT_DEFINED",
          "subAvailabilityImpact": "NONE",
          "subConfidentialityImpact": "NONE",
          "subIntegrityImpact": "NONE",
          "userInteraction": "NONE",
          "valueDensity": "NOT_DEFINED",
          "vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
          "version": "4.0",
          "vulnAvailabilityImpact": "NONE",
          "vulnConfidentialityImpact": "LOW",
          "vulnIntegrityImpact": "LOW",
          "vulnerabilityResponseEffort": "NOT_DEFINED"
        },
        "source": "596c5446-0ce5-4ba2-aa66-48b3b757a647",
        "type": "Secondary"
      }
    ]
  },
  "published": "2026-11-06T13:17:29.950",
  "references": [
    {
      "source": "596c5446-0ce5-4ba2-aa66-48b3b757a647",
      "url": "https://github.com/symfony/symfony/commit/af0aae5012beedf0a0c3fd581fd8b9ef696240c4"
    },
    {
      "source": "596c5446-0ce5-4ba2-aa66-48b3b757a647",
      "url": "https://github.com/symfony/symfony/security/advisories/GHSA-8f57-m8wj-x65w"
    }
  ],
  "sourceIdentifier": "596c5446-0ce5-4ba2-aa66-48b3b757a647",
  "vulnStatus": "Awaiting Analysis",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-288"
        }
      ],
      "source": "596c5446-0ce5-4ba2-aa66-48b3b757a647",
      "type": "Secondary"
    }
  ]
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

Order JSON

How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Publication & reservation Sightings KEV catalogs Other timestamps

Loading timeline…

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.

Action not permitted