CVE-2026-118514 (GCVE-0-2026-118514)

Vulnerability from cvelistv5 – Published: 2026-11-06 14:09 – Updated: 2026-11-06 14:09
VLAI
Title
Symfony: HEAD Requests Bypass the methods Option of security.access_control Rules and Firewalls
Summary
In Symfony http-foundation prior to versions 5.4.56, 6.4.50, 7.4.23, and 8.1.11, Symfony\Component\HttpFoundation\RequestMatcher, and RequestMatcher\MethodRequestMatcher which replaces it from 6.2.x on, matches a request against a list of HTTP methods. These compared the request method to the list verbatim, while the router serves a HEAD request with the GET handler, as HTTP semantics require. This came after the incomplete fix of  CVE-2026-45075 https://github.com/advisories/GHSA-6439-2f28-8p8q , which addressed the same gap in the #[IsGranted], #[IsSignatureValid] and #[IsCsrfTokenValid] attributes only. Security rules configured to apply only to GET requests could therefore be bypassed by sending a HEAD request to the same URL. Although HEAD responses contain no body, attackers could still access response headers and trigger the controller's execution, including any side effects. This issue also affects firewalls configured with methods: [GET]. A HEAD request would not match that firewall and could instead be handled by another matching firewall or no firewall at all. Applications using these vulnerable request matchers directly, including through a custom firewall request_matcher, could also be affected. The issue affects symfony/http-foundation through v5.4.55, v6.x through 6.4.49, v7.x through v7.4.22, and v8.x through v8.1.10.
Severity
6.3 (Medium)
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
CWE
Assigner
Checkmarx CNA
References
Impacted products
Vendor Product Version
symfony symfony Affected: 0 , < 5.4.56 (git)
Affected: 6 , < 6.4.50 (git)
Affected: 7 , < 7.4.23 (git)
Affected: 8 , < 8.1.11 (git)
Create a notification for this product.
Credits
Ivan Tse Nicolas Grekas
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "collectionURL": "https://packagist.org/packages/symfony/http-foundation",
          "defaultStatus": "unaffected",
          "packageName": "symfony/http-foundation",
          "product": "symfony",
          "repo": "https://github.com/symfony/http-foundation",
          "vendor": "symfony",
          "versions": [
            {
              "lessThan": "5.4.56",
              "status": "affected",
              "version": "0",
              "versionType": "git"
            },
            {
              "lessThan": "6.4.50",
              "status": "affected",
              "version": "6",
              "versionType": "git"
            },
            {
              "lessThan": "7.4.23",
              "status": "affected",
              "version": "7",
              "versionType": "git"
            },
            {
              "lessThan": "8.1.11",
              "status": "affected",
              "version": "8",
              "versionType": "git"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "reporter",
          "value": "Ivan Tse"
        },
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "Nicolas Grekas"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cdiv\u003eIn Symfony http-foundation prior to versions 5.4.56, 6.4.50, 7.4.23, and 8.1.11,\u0026nbsp;\u003ccode\u003eSymfony\\Component\\HttpFoundation\\RequestMatcher,\u003c/code\u003e\u0026nbsp;and\u0026nbsp;\u003ccode\u003eRequestMatcher\\MethodRequestMatcher\u003c/code\u003e\u0026nbsp;which replaces it from 6.2.x on, matches a request against a list of HTTP methods.\u0026nbsp;These compared the request method to the list verbatim, while the router serves a\u0026nbsp;\u003ccode\u003eHEAD\u003c/code\u003e\u0026nbsp;request with the\u0026nbsp;\u003ccode\u003eGET\u003c/code\u003e\u0026nbsp;handler, as HTTP semantics require.\u003cbr\u003e\u003cbr\u003eThis came after the incomplete fix of\u0026nbsp;\u003ca title=\"CVE-2026-45075\" href=\"https://github.com/advisories/GHSA-6439-2f28-8p8q\" rel=\"noreferrer\"\u003eCVE-2026-45075\u003c/a\u003e, which\u0026nbsp;addressed the same gap in the \u003ccode\u003e#[IsGranted]\u003c/code\u003e, \u003ccode\u003e#[IsSignatureValid]\u003c/code\u003e and \u003ccode\u003e#[IsCsrfTokenValid]\u003c/code\u003e attributes only.\u003cbr\u003e\u003cbr\u003e\u003cp\u003eSecurity rules configured to apply only to \u003ccode\u003eGET\u003c/code\u003e requests could therefore be bypassed by sending a \u003ccode\u003eHEAD\u003c/code\u003e request to the same URL. Although \u003ccode\u003eHEAD\u003c/code\u003e responses contain no body, attackers could still access response headers and trigger the controller\u0027s execution, including any side effects.\u003c/p\u003e\u003cp\u003eThis issue also affects firewalls configured with \u003ccode\u003emethods: [GET]\u003c/code\u003e. A\u0026nbsp;\u003ccode\u003eHEAD\u003c/code\u003e request would not match that firewall and could instead be handled by another matching firewall or no firewall at all. Applications using these vulnerable request matchers directly, including through a custom firewall \u003ccode\u003erequest_matcher\u003c/code\u003e, could also be affected.\u003c/p\u003e\u003c/div\u003e\u003cdiv\u003eThe issue affects\u0026nbsp;\u003ccode\u003esymfony/http-foundation\u003c/code\u003e\u0026nbsp;through v5.4.55, v6.x through 6.4.49, v7.x through v7.4.22, and v8.x through v8.1.10.\u003c/div\u003e"
            }
          ],
          "value": "In Symfony http-foundation prior to versions 5.4.56, 6.4.50, 7.4.23, and 8.1.11,\u00a0Symfony\\Component\\HttpFoundation\\RequestMatcher,\u00a0and\u00a0RequestMatcher\\MethodRequestMatcher\u00a0which replaces it from 6.2.x on, matches a request against a list of HTTP methods.\u00a0These compared the request method to the list verbatim, while the router serves a\u00a0HEAD\u00a0request with the\u00a0GET\u00a0handler, as HTTP semantics require.\n\nThis came after the incomplete fix of\u00a0 CVE-2026-45075 https://github.com/advisories/GHSA-6439-2f28-8p8q , which\u00a0addressed the same gap in the #[IsGranted], #[IsSignatureValid] and #[IsCsrfTokenValid] attributes only.\n\n\n\nSecurity rules configured to apply only to GET requests could therefore be bypassed by sending a HEAD request to the same URL. Although HEAD responses contain no body, attackers could still access response headers and trigger the controller\u0027s execution, including any side effects.\n\n\n\nThis issue also affects firewalls configured with methods: [GET]. A\u00a0HEAD request would not match that firewall and could instead be handled by another matching firewall or no firewall at all. Applications using these vulnerable request matchers directly, including through a custom firewall request_matcher, could also be affected.\n\n\n\nThe issue affects\u00a0symfony/http-foundation\u00a0through v5.4.55, v6.x through 6.4.49, v7.x through v7.4.22, and v8.x through v8.1.10."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "Automatable": "NOT_DEFINED",
            "Recovery": "NOT_DEFINED",
            "Safety": "NOT_DEFINED",
            "attackComplexity": "LOW",
            "attackRequirements": "PRESENT",
            "attackVector": "NETWORK",
            "baseScore": 6.3,
            "baseSeverity": "MEDIUM",
            "exploitMaturity": "NOT_DEFINED",
            "privilegesRequired": "NONE",
            "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:N/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-863",
              "description": "CWE-863",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-06T14:09:56.213Z",
        "orgId": "596c5446-0ce5-4ba2-aa66-48b3b757a647",
        "shortName": "Checkmarx"
      },
      "references": [
        {
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://github.com/symfony/symfony/security/advisories/GHSA-jrf8-gvm4-7cgh"
        },
        {
          "tags": [
            "patch"
          ],
          "url": "https://github.com/symfony/symfony/commit/cd20e9f8f16d1f0df6c2eac19bdb649325a192bd"
        },
        {
          "tags": [
            "patch"
          ],
          "url": "https://github.com/symfony/symfony/commit/13a8b85be687499cbc69a534ada16683f9ba3889"
        }
      ],
      "source": {
        "discovery": "UNKNOWN"
      },
      "title": "Symfony: HEAD Requests Bypass the methods Option of security.access_control Rules and Firewalls",
      "x_generator": {
        "engine": "Vulnogram 1.0.5"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "596c5446-0ce5-4ba2-aa66-48b3b757a647",
    "assignerShortName": "Checkmarx",
    "cveId": "CVE-2026-118514",
    "datePublished": "2026-11-06T14:09:56.213Z",
    "dateReserved": "2026-10-28T14:33:36.992Z",
    "dateUpdated": "2026-11-06T14:09:56.213Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

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

JSON

Loading timeline…




    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.