GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

FKIE_CVE-2026-53718

Vulnerability from fkie_nvd - Published: 2026-09-14 21:17 - Updated: 2026-09-14 21:17
Severity
6.4 (Medium) - CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:L
Summary
Envoy Gateway is an open source project for managing Envoy Proxy as a standalone or Kubernetes-based application gateway. Prior to 1.7.4 and 1.8.1, an HTTPRoute can use an extension-managed custom backendRef to reference a backend resource in another namespace without a matching Gateway API ReferenceGrant in the target namespace. The custom-backend branch in internal/gatewayapi/route.go omits validateBackendNamespace, allowing the route-owning namespace to bind to and use the resource without the backend namespace owner's consent and violating the Gateway API cross-namespace authorization model. This issue is fixed in versions 1.7.4 and 1.8.1.
References
security-advisories@github.comhttps://github.com/envoyproxy/gateway/commit/5a78db82b7cf4fc5bebbeda2c50952892038a464
security-advisories@github.comhttps://github.com/envoyproxy/gateway/commit/96e2b750868a459ace4b8b68e6a6e4fb0152b9b7
security-advisories@github.comhttps://github.com/envoyproxy/gateway/commit/b4737180c7e597490c6363075c565fa8cf24eead
security-advisories@github.comhttps://github.com/envoyproxy/gateway/pull/9171
security-advisories@github.comhttps://github.com/envoyproxy/gateway/pull/9172
security-advisories@github.comhttps://github.com/envoyproxy/gateway/pull/9173
security-advisories@github.comhttps://github.com/envoyproxy/gateway/releases/tag/v1.7.4
security-advisories@github.comhttps://github.com/envoyproxy/gateway/releases/tag/v1.8.1
security-advisories@github.comhttps://github.com/envoyproxy/gateway/security/advisories/GHSA-fcrp-7gc2-93g7
Impacted products
Vendor Product Version
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "product": "gateway",
          "vendor": "envoyproxy",
          "versions": [
            {
              "status": "affected",
              "version": "\u003c 1.7.4"
            },
            {
              "status": "affected",
              "version": "\u003e= 1.8.0-rc.0, \u003c 1.8.1"
            }
          ]
        }
      ],
      "source": "security-advisories@github.com"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "Envoy Gateway is an open source project for managing Envoy Proxy as a standalone or Kubernetes-based application gateway. Prior to 1.7.4 and 1.8.1, an HTTPRoute can use an extension-managed custom backendRef to reference a backend resource in another namespace without a matching Gateway API ReferenceGrant in the target namespace. The custom-backend branch in internal/gatewayapi/route.go omits validateBackendNamespace, allowing the route-owning namespace to bind to and use the resource without the backend namespace owner\u0027s consent and violating the Gateway API cross-namespace authorization model. This issue is fixed in versions 1.7.4 and 1.8.1."
    }
  ],
  "id": "CVE-2026-53718",
  "lastModified": "2026-09-14T21:17:13.140",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "HIGH",
          "attackVector": "NETWORK",
          "availabilityImpact": "LOW",
          "baseScore": 6.4,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "LOW",
          "privilegesRequired": "LOW",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:L",
          "version": "3.1"
        },
        "exploitabilityScore": 1.6,
        "impactScore": 4.7,
        "source": "security-advisories@github.com",
        "type": "Secondary"
      }
    ]
  },
  "published": "2026-09-14T21:17:13.140",
  "references": [
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/envoyproxy/gateway/commit/5a78db82b7cf4fc5bebbeda2c50952892038a464"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/envoyproxy/gateway/commit/96e2b750868a459ace4b8b68e6a6e4fb0152b9b7"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/envoyproxy/gateway/commit/b4737180c7e597490c6363075c565fa8cf24eead"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/envoyproxy/gateway/pull/9171"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/envoyproxy/gateway/pull/9172"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/envoyproxy/gateway/pull/9173"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/envoyproxy/gateway/releases/tag/v1.7.4"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/envoyproxy/gateway/releases/tag/v1.8.1"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/envoyproxy/gateway/security/advisories/GHSA-fcrp-7gc2-93g7"
    }
  ],
  "sourceIdentifier": "security-advisories@github.com",
  "vulnStatus": "Received",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-862"
        }
      ],
      "source": "security-advisories@github.com",
      "type": "Primary"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





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.


Detection rules are retrieved from Rulezet.