CVE-2026-49336

{"id": "CVE-2026-49336", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-49336", "role": "CISA Coordinator", "options": [{"exploitation": "poc"}, {"automatable": "yes"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-06-22T15:05:06.323889Z"}}], "cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 5.5, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/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": "PROOF_OF_CONCEPT", "providerUrgency": "NOT_DEFINED", "userInteraction": "NONE", "attackComplexity": "LOW", "attackRequirements": "NONE", "privilegesRequired": "NONE", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "NONE", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "NONE", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "LOW", "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"}}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "microsoft", "product": "kiota-typescript", "versions": [{"status": "affected", "version": ">= 1.0.0-preview.97, < 1.0.0-preview.102"}]}]}], "published": "2026-06-19T19:16:36.430", "references": [{"url": "https://github.com/microsoft/kiota-typescript/commit/09f8bd9b34d68bf412a9b78f6ca7e7961ef14974", "source": "security-advisories@github.com"}, {"url": "https://github.com/microsoft/kiota-typescript/security/advisories/GHSA-396q-4vc8-28x9", "source": "security-advisories@github.com"}, {"url": "https://github.com/microsoft/kiota-typescript/security/advisories/GHSA-396q-4vc8-28x9", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-178"}, {"lang": "en", "value": "CWE-200"}]}], "descriptions": [{"lang": "en", "value": "@microsoft/kiota-http-fetchlibrary provides TypeScript libraries for Kiota-generated API clients. In versions 1.0.0-preview.97 through 1.0.0-preview.101, `@microsoft/kiota-http-fetchlibrary`'s `RedirectHandler` is documented as stripping `Authorization` and `Cookie` from cross-origin redirect targets, but the default `scrubSensitiveHeaders` callback in `RedirectHandlerOptions` uses case-sensitive property deletion (`delete headers.Authorization`, `delete headers.Cookie`) on a headers object that `FetchRequestAdapter.getRequestFromRequestInformation` has already lower-cased. The delete therefore targets keys that do not exist, the scrub is a no-op, and any Bearer token or Cookie attached by a kiota-generated SDK is forwarded to an attacker-controlled host across a 30x redirect. This is reachable in the default middleware chain (`MiddlewareFactory.getDefaultMiddlewares`) with no custom configuration, and applies to every kiota-generated TypeScript SDK that uses `BaseBearerTokenAuthenticationProvider` or any other authentication provider that sets the `Authorization` request header. Version 1.0.0-preview.102 patches the issue."}, {"lang": "es", "value": "@microsoft/kiota-http-fetchlibrary proporciona bibliotecas TypeScript para clientes API generados por Kiota. En las versiones 1.0.0-preview.97 a 1.0.0-preview.101, el \u2019RedirectHandler\u2019 de \u2019@microsoft/kiota-http-fetchlibrary\u2019 est\u00e1 documentado como que elimina \u2019Authorization\u2019 y \u2019Cookie\u2019 de los destinos de redirecci\u00f3n de origen cruzado, pero la devoluci\u00f3n de llamada predeterminada \u2019scrubSensitiveHeaders\u2019 en \u2019RedirectHandlerOptions\u2019 utiliza la eliminaci\u00f3n de propiedades que distingue entre may\u00fasculas y min\u00fasculas (\u2019delete headers.Authorization\u2019, \u2019delete headers.Cookie\u2019) en un objeto de encabezados que \u2019FetchRequestAdapter.getRequestFromRequestInformation\u2019 ya ha convertido a min\u00fasculas. Por lo tanto, la eliminaci\u00f3n apunta a claves que no existen, la limpieza es una operaci\u00f3n nula, y cualquier token Bearer o cookie adjuntado por un SDK generado por Kiota se reenv\u00eda a un host controlado por el atacante a trav\u00e9s de una redirecci\u00f3n 30x. Esto es accesible en la cadena de middleware predeterminada (\u2019MiddlewareFactory.getDefaultMiddlewares\u2019) sin configuraci\u00f3n personalizada, y se aplica a cada SDK TypeScript generado por Kiota que utiliza \u2019BaseBearerTokenAuthenticationProvider\u2019 o cualquier otro proveedor de autenticaci\u00f3n que establece el encabezado de solicitud \u2019Authorization\u2019. La versi\u00f3n 1.0.0-preview.102 corrige el problema."}], "lastModified": "2026-10-25T23:10:00.167", "sourceIdentifier": "security-advisories@github.com"}