CVE-2026-55666

Rocket.Chat is an open-source, secure, fully customizable communications platform. Prior to 8.5.1, 8.4.4, 8.3.6, 8.2.6, 8.1.6, 8.0.7, and 7.10.13, in apps/meteor/app/apple/server/loginHandler.ts, handleIdentityToken parses a JWT issued by Apple during the OAuth flow. The try block checks for an email parameter. If the JWT does not contain an email address, the application falls back to accepting an arbitrary email value supplied directly in the request. Attackers are able to forge Apple JWTs that do not contain an email address and leverage this vulnerability to carry out account takeover attacks. This vulnerability is fixed in 8.5.1, 8.4.4, 8.3.6, 8.2.6, 8.1.6, 8.0.7, and 7.10.13.

CVSS

No CVSS.

References

Link	Resource
https://github.com/RocketChat/Rocket.Chat/security/advisories/GHSA-wx3c-76rf-wpwf

Configurations

No configuration.

History

25 Oct 2026, 23:10

Type	Values Removed	Values Added
Summary		(es) Rocket.Chat es una plataforma de comunicaciones de código abierto, segura y totalmente personalizable. Antes de las versiones 8.5.1, 8.4.4, 8.3.6, 8.2.6, 8.1.6, 8.0.7 y 7.10.13, en apps/meteor/app/apple/servidor/loginHandler.ts, handleIdentityToken analiza un JWT emitido por Apple durante el flujo de OAuth. El bloque try verifica un parámetro de correo electrónico. Si el JWT no contiene una dirección de correo electrónico, la aplicación recurre a aceptar un valor de correo electrónico arbitrario suministrado directamente en la solicitud. Los atacantes pueden falsificar JWT de Apple que no contienen una dirección de correo electrónico y aprovechar esta vulnerabilidad para llevar a cabo ataques de toma de control de cuentas. Esta vulnerabilidad está corregida en las versiones 8.5.1, 8.4.4, 8.3.6, 8.2.6, 8.1.6, 8.0.7 y 7.10.13.

Information

Published : 2026-06-24 22:16

Updated : 2026-10-25 23:10

NVD link : CVE-2026-55666

Mitre link : CVE-2026-55666

CVE.ORG link : CVE-2026-55666

JSON object : View

Products Affected

No product.

CWE

CWE-287

Improper Authentication

CWE-288

Authentication Bypass Using an Alternate Path or Channel

{"id": "CVE-2026-55666", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-55666", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "yes"}, {"technicalImpact": "total"}], "version": "2.0.3", "timestamp": "2026-06-26T03:55:30.444148Z"}}], "cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 9.3, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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": "NONE", "attackComplexity": "LOW", "attackRequirements": "NONE", "privilegesRequired": "NONE", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "HIGH", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "HIGH", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "HIGH", "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": "RocketChat", "product": "Rocket.Chat", "versions": [{"status": "affected", "version": ">= 8.5.0-rc.0, < 8.5.1"}, {"status": "affected", "version": ">= 8.4.0-rc.0, < 8.4.4"}, {"status": "affected", "version": ">= 8.3.0-rc.0, < 8.3.6"}, {"status": "affected", "version": ">= 8.2.0-rc.0, < 8.2.6"}, {"status": "affected", "version": ">= 8.1.0-rc.0, < 8.1.6"}, {"status": "affected", "version": ">= 7.11.0-rc.0, < 8.0.7"}, {"status": "affected", "version": "< 7.10.13"}]}]}], "published": "2026-06-24T22:16:49.393", "references": [{"url": "https://github.com/RocketChat/Rocket.Chat/security/advisories/GHSA-wx3c-76rf-wpwf", "source": "security-advisories@github.com"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-287"}, {"lang": "en", "value": "CWE-288"}]}], "descriptions": [{"lang": "en", "value": "Rocket.Chat is an open-source, secure, fully customizable communications platform. Prior to 8.5.1, 8.4.4, 8.3.6, 8.2.6, 8.1.6, 8.0.7, and 7.10.13, in apps/meteor/app/apple/server/loginHandler.ts, handleIdentityToken parses a JWT issued by Apple during the OAuth flow. The try block checks for an email parameter. If the JWT does not contain an email address, the application falls back to accepting an arbitrary email value supplied directly in the request. Attackers are able to forge Apple JWTs that do not contain an email address and leverage this vulnerability to carry out account takeover attacks. This vulnerability is fixed in 8.5.1, 8.4.4, 8.3.6, 8.2.6, 8.1.6, 8.0.7, and 7.10.13."}, {"lang": "es", "value": "Rocket.Chat es una plataforma de comunicaciones de c\u00f3digo abierto, segura y totalmente personalizable. Antes de las versiones 8.5.1, 8.4.4, 8.3.6, 8.2.6, 8.1.6, 8.0.7 y 7.10.13, en apps/meteor/app/apple/servidor/loginHandler.ts, handleIdentityToken analiza un JWT emitido por Apple durante el flujo de OAuth. El bloque try verifica un par\u00e1metro de correo electr\u00f3nico. Si el JWT no contiene una direcci\u00f3n de correo electr\u00f3nico, la aplicaci\u00f3n recurre a aceptar un valor de correo electr\u00f3nico arbitrario suministrado directamente en la solicitud. Los atacantes pueden falsificar JWT de Apple que no contienen una direcci\u00f3n de correo electr\u00f3nico y aprovechar esta vulnerabilidad para llevar a cabo ataques de toma de control de cuentas. Esta vulnerabilidad est\u00e1 corregida en las versiones 8.5.1, 8.4.4, 8.3.6, 8.2.6, 8.1.6, 8.0.7 y 7.10.13."}], "lastModified": "2026-10-25T23:10:00.167", "sourceIdentifier": "security-advisories@github.com"}