CVE-2026-65655

{"id": "CVE-2026-65655", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-65655", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-08-11T20:15:46.742171Z"}}], "cvssMetricV40": [{"type": "Secondary", "source": "security@temporal.io", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 2.3, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "LOW", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/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", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "PASSIVE", "attackComplexity": "LOW", "attackRequirements": "PRESENT", "privilegesRequired": "NONE", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "LOW", "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@temporal.io", "affectedData": [{"repo": "https://github.com/temporalio/ui-server", "vendor": "Temporal Technologies, Inc.", "modules": ["OIDC authentication cookies"], "product": "Temporal UI Server", "versions": [{"status": "affected", "version": "2.7.0", "lessThan": "2.53.2", "versionType": "semver"}], "packageName": "github.com/temporalio/ui-server/v2", "programFiles": ["server/auth/auth.go", "server/route/auth.go"], "collectionURL": "https://pkg.go.dev", "defaultStatus": "unaffected"}]}], "published": "2026-08-11T20:18:31.447", "references": [{"url": "https://github.com/temporalio/ui-server/blob/v2.53.1/server/auth/auth.go#L87-L153", "source": "security@temporal.io"}, {"url": "https://github.com/temporalio/ui-server/blob/v2.53.1/server/route/auth.go#L281-L316", "source": "security@temporal.io"}, {"url": "https://github.com/temporalio/ui-server/commit/7b9ff533fb51beba75497c0a192c66775c08f279", "source": "security@temporal.io"}, {"url": "https://github.com/temporalio/ui-server/commit/821cf598371353f1b579dfe1e87aeb3638b041d6", "source": "security@temporal.io"}, {"url": "https://github.com/temporalio/ui-server/commit/8876b80b63003688ab736f45ef28885695a4f6db", "source": "security@temporal.io"}, {"url": "https://github.com/temporalio/ui-server/releases/tag/v2.53.1", "source": "security@temporal.io"}, {"url": "https://github.com/temporalio/ui-server/releases/tag/v2.53.2", "source": "security@temporal.io"}, {"url": "https://github.com/temporalio/ui/pull/3806", "source": "security@temporal.io"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security@temporal.io", "description": [{"lang": "en", "value": "CWE-614"}]}], "descriptions": [{"lang": "en", "value": "When OAuth authentication is enabled and browser-facing TLS terminates at a reverse proxy that forwards the callback to Temporal UI Server over HTTP, affected versions derive authentication-cookie Secure attributes from the proxy-to-server connection. Temporal UI Server can therefore issue access-token cookies, and refresh-token cookies when provided by the identity provider, without Secure even though the browser completed login over HTTPS.\n\n\n\nA victim who visits attacker-controlled content while a credential remains live may expose that credential only if the attacker can also steer traffic for the UI hostname, prevent the browser's HTTPS connection from succeeding, serve the hostname over HTTP, and read a later same-site plaintext request. A malicious website alone cannot read the cookie, and passive observation of a successful TLS connection is insufficient. Effective HSTS, a blocking HTTPS-only warning, or TLS re-encryption between the proxy and Temporal UI Server prevents the demonstrated disclosure path.\n\n\n\nA recovered credential may be replayed within the victim's assigned permissions. Refresh-token replay additionally depends on the identity provider's issuance, expiry, rotation, and reuse-detection behavior."}, {"lang": "es", "value": "Cuyo la autenticaci\u00f3n OAuth est\u00e1 habilitada y el TLS orientado al navegador termina en un proxy inverso que reenv\u00eda la devoluci\u00f3n de llamada al Temporal UI Server a trav\u00e9s de HTTP, las versiones afectadas derivan los atributos Secure de la cookie de autenticaci\u00f3n de la conexi\u00f3n entre el proxy y el servidor. El Temporal UI Server puede, por lo tanto, emitir cookies de token de acceso y cookies de token de actualizaci\u00f3n cuyo las proporciona el proveedor de identidad, sin Secure, a pesar de que el navegador complet\u00f3 el inicio de sesi\u00f3n a trav\u00e9s de HTTPS.\n\nUna v\u00edctima que visita contenido controlado por el atacante mientras una credencial permanece activa puede exponer esa credencial solo si el atacante tambi\u00e9n puede dirigir el tr\u00e1fico para el nombre de host de la interfaz de usuario, evitar que la conexi\u00f3n HTTPS del navegador tenga \u00e9xito, servir el nombre de host a trav\u00e9s de HTTP y leer una solicitud posterior de texto sin cifrar del mismo sitio. Un sitio web malicioso por s\u00ed solo no puede leer la cookie, y la observaci\u00f3n pasiva de una conexi\u00f3n TLS exitosa es insuficiente. HSTS efectivo, una advertencia de solo HTTPS que bloquea, o el recifrado TLS entre el proxy y el Temporal UI Server previene la ruta de divulgaci\u00f3n demostrada.\n\nUna credencial recuperada puede ser reproducida dentro de los permisos asignados a la v\u00edctima. La reproducci\u00f3n del token de actualizaci\u00f3n depende adicionalmente de la emisi\u00f3n del proveedor de identidad, la caducidad, la rotaci\u00f3n y el comportamiento de detecci\u00f3n de reutilizaci\u00f3n."}], "lastModified": "2026-10-24T16:10:00.153", "sourceIdentifier": "security@temporal.io"}