CVE-2026-2836

{"id": "CVE-2026-2836", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 8.1, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "REQUIRED", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.2, "exploitabilityScore": 2.8}], "cvssMetricV40": [{"type": "Secondary", "source": "cna@cloudflare.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 8.4, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "HIGH", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:N/SC:H/SI:H/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", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "PASSIVE", "attackComplexity": "LOW", "attackRequirements": "NONE", "privilegesRequired": "NONE", "subIntegrityImpact": "HIGH", "vulnIntegrityImpact": "HIGH", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "NONE", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "HIGH", "vulnConfidentialityImpact": "NONE", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "published": "2026-03-05T00:15:58.053", "references": [{"url": "https://github.com/cloudflare/pingora", "tags": ["Product"], "source": "cna@cloudflare.com"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "description": [{"lang": "en", "value": "CWE-345"}]}], "descriptions": [{"lang": "en", "value": "A cache poisoning vulnerability has been found in the Pingora HTTP proxy framework\u2019s default cache key construction. The issue occurs because the default HTTP cache key implementation generates cache keys using only the URI path, excluding critical factors such as the host header (authority). Operators relying on the default are vulnerable to cache poisoning, and cross-origin responses may be improperly served to users.\n\n\nImpact\n\nThis vulnerability affects users of Pingora's alpha proxy caching feature who relied on the default CacheKey implementation. An attacker could exploit this for:\n\n * Cross-tenant data leakage: In multi-tenant deployments, poison the cache so that users from one tenant receive cached responses from another tenant\n\n\n * Cache poisoning attacks: Serve malicious content to legitimate users by poisoning shared cache entries\n\n\n\n\nCloudflare's CDN infrastructure was not affected by this vulnerability, as Cloudflare's default cache key implementation uses multiple factors to prevent cache key poisoning and never made use of the previously provided default.\n\n\nMitigation:\n\nWe strongly recommend Pingora users to upgrade to Pingora v0.8.0 or higher, which removes the insecure default cache key implementation. Users must now explicitly implement their own callback that includes appropriate factors such as Host header, origin server HTTP scheme, and other attributes their cache should vary on.\n\n\nPingora users on previous versions may also remove any of their default CacheKey usage and implement their own that should at minimum include the host header / authority and upstream peer\u2019s HTTP scheme."}, {"lang": "es", "value": "Se ha encontrado una vulnerabilidad de envenenamiento de cach\u00e9 en la construcci\u00f3n predeterminada de clave de cach\u00e9 del framework de proxy HTTP Pingora. El problema ocurre porque la implementaci\u00f3n predeterminada de clave de cach\u00e9 HTTP genera claves de cach\u00e9 usando solo la ruta URI, excluyendo factores cr\u00edticos como el encabezado de host (autoridad). Los operadores que dependen del valor predeterminado son vulnerables al envenenamiento de cach\u00e9, y las respuestas de origen cruzado pueden ser servidas incorrectamente a los usuarios.\n\nImpacto\n\nEsta vulnerabilidad afecta a los usuarios de la caracter\u00edstica de almacenamiento en cach\u00e9 de proxy alfa de Pingora que depend\u00edan de la implementaci\u00f3n predeterminada de CacheKey. Un atacante podr\u00eda explotar esto para:\n\n * Fuga de datos entre inquilinos: En implementaciones multi-inquilino, envenenar la cach\u00e9 para que los usuarios de un inquilino reciban respuestas en cach\u00e9 de otro inquilino\n\n * Ataques de envenenamiento de cach\u00e9: Servir contenido malicioso a usuarios leg\u00edtimos envenenando entradas de cach\u00e9 compartidas\n\nLa infraestructura CDN de Cloudflare no se vio afectada por esta vulnerabilidad, ya que la implementaci\u00f3n predeterminada de clave de cach\u00e9 de Cloudflare utiliza m\u00faltiples factores para prevenir el envenenamiento de clave de cach\u00e9 y nunca hizo uso del valor predeterminado proporcionado anteriormente.\n\nMitigaci\u00f3n:\n\nRecomendamos encarecidamente a los usuarios de Pingora que actualicen a Pingora v0.8.0 o superior, lo que elimina la implementaci\u00f3n predeterminada insegura de clave de cach\u00e9. Los usuarios ahora deben implementar expl\u00edcitamente su propia funci\u00f3n de devoluci\u00f3n de llamada que incluya factores apropiados como el encabezado Host, el esquema HTTP del servidor de origen y otros atributos en los que su cach\u00e9 deber\u00eda variar.\n\nLos usuarios de Pingora en versiones anteriores tambi\u00e9n pueden eliminar cualquier uso de su CacheKey predeterminada e implementar la suya propia que deber\u00eda incluir como m\u00ednimo el encabezado de host / autoridad y el esquema HTTP del par ascendente."}], "lastModified": "2026-03-12T14:33:32.573", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:cloudflare:pingora:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "7FD8B659-5061-46DA-8A73-2E17D6298546", "versionEndExcluding": "0.8.0"}], "operator": "OR"}]}], "sourceIdentifier": "cna@cloudflare.com"}