CVE-2026-66884

{"id": "CVE-2026-66884", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-66884", "role": "CISA Coordinator", "options": [{"exploitation": "poc"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-08-04T12:37:09.321822Z"}}], "cvssMetricV40": [{"type": "Secondary", "source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 2.1, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "LOW", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/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": "ACTIVE", "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": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db", "affectedData": [{"cpes": ["cpe:2.3:a:erlef:oidcc_plug:*:*:*:*:*:erlang:*:*"], "repo": "https://github.com/erlef/oidcc_plug", "vendor": "Erlang Ecosystem Foundation", "modules": ["Elixir.Oidcc.Plug.AuthorizationCallback"], "product": "oidcc_plug", "versions": [{"status": "affected", "version": "0.2.0-beta.1", "lessThan": "0.5.0", "versionType": "semver"}], "packageURL": "pkg:hex/oidcc_plug", "packageName": "oidcc_plug", "programFiles": ["lib/oidcc/plug/authorization_callback.ex"], "collectionURL": "https://repo.hex.pm", "defaultStatus": "unaffected", "programRoutines": [{"name": "'Elixir.Oidcc.Plug.AuthorizationCallback':call/2"}]}, {"cpes": ["cpe:2.3:a:erlef:oidcc_plug:*:*:*:*:*:erlang:*:*"], "repo": "https://github.com/erlef/oidcc_plug", "vendor": "Erlang Ecosystem Foundation", "modules": ["Elixir.Oidcc.Plug.AuthorizationCallback"], "product": "oidcc_plug", "versions": [{"status": "affected", "version": "e577ae73b9080693442916043a22d8f05491dd93", "lessThan": "97d75afc57826dca31989b47d6e2a3c136039917", "versionType": "git"}], "packageURL": "pkg:github/erlef/oidcc_plug", "packageName": "erlef/oidcc_plug", "programFiles": ["lib/oidcc/plug/authorization_callback.ex"], "collectionURL": "https://github.com", "defaultStatus": "unaffected", "programRoutines": [{"name": "'Elixir.Oidcc.Plug.AuthorizationCallback':call/2"}]}]}], "published": "2026-08-04T12:16:36.373", "references": [{"url": "https://cna.erlef.org/cves/CVE-2026-66884.html", "source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db"}, {"url": "https://github.com/erlef/oidcc_plug/commit/97d75afc57826dca31989b47d6e2a3c136039917", "source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db"}, {"url": "https://github.com/erlef/oidcc_plug/security/advisories/GHSA-fg66-w5gp-22cr", "source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db"}, {"url": "https://osv.dev/vulnerability/EEF-CVE-2026-66884", "source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db"}, {"url": "https://github.com/erlef/oidcc_plug/security/advisories/GHSA-fg66-w5gp-22cr", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db", "description": [{"lang": "en", "value": "CWE-352"}]}], "descriptions": [{"lang": "en", "value": "Cross-Site Request Forgery vulnerability in Erlang Ecosystem Foundation oidcc_plug (Oidcc.Plug.AuthorizationCallback module) allows an attacker to make a victim's browser complete an authorization flow the victim never initiated.\n\nThis vulnerability is associated with program file lib/oidcc/plug/authorization_callback.ex and program routine Oidcc.Plug.AuthorizationCallback.call/2.\n\nA callback request that carries no Oidcc.Plug.Authorize session is processed with every security check disabled rather than being rejected. call/2 substitutes permissive defaults for the absent session, and each downstream check treats its value as nothing to compare and returns :ok, so the nonce, state, PKCE, peer IP and user agent checks are all skipped. A separate clause of check_state/2 also accepts a state-less request when a verifier is present.\n\nAn attacker obtains an authorization code for their own provider account, then induces the victim to visit the callback endpoint with that code and no state parameter. The application signs the victim in as the attacker, so the victim's subsequent actions occur in the attacker's account where the attacker can read them. Applications reusing one callback for both signing in and linking a provider account are further exposed to account takeover, the attacker's account becoming linked to the victim's.\n\nThe permissive fallback serves no conforming flow. Third-party-initiated login reaches a relying party at a separate login initiation endpoint and causes it to send a fresh authentication request, and this library implements no such endpoint. Oidcc.Plug.Authorize always sends a state parameter, which an authorization server must echo, so no legitimate callback lacks one.\n\nThis issue affects oidcc_plug: from 0.2.0-beta.1 before 0.5.0."}, {"lang": "es", "value": "Vulnerabilidad de falsificaci\u00f3n de petici\u00f3n en sitios cruzados en Erlang Ecosystem Foundation oidcc_plug (m\u00f3dulo Oidcc.Plug.AuthorizationCallback) permite a un atacante hacer que el navegador de una v\u00edctima complete un flujo de autorizaci\u00f3n que la v\u00edctima nunca inici\u00f3.\n\nEsta vulnerabilidad est\u00e1 asociada con el archivo de programa lib/oidcc/plug/authorization_callback.ex y la rutina de programa Oidcc.Plug.AuthorizationCallback.call/2.\n\nUna petici\u00f3n de devoluci\u00f3n de llamada que no lleva ninguna sesi\u00f3n de Oidcc.Plug.Authorize se procesa con todas las verificaciones de seguridad deshabilitadas en lugar de ser rechazada. call/2 sustituye valores predeterminados permisivos para la sesi\u00f3n ausente, y cada verificaci\u00f3n posterior trata su valor como nada que comparar y devuelve :ok, por lo que las verificaciones de nonce, estado, PKCE, IP del par y agente de usuario son todas omitidas. Una cl\u00e1usula separada de check_state/2 tambi\u00e9n acepta una petici\u00f3n sin estado cuando un verificador est\u00e1 presente.\n\nUn atacante obtiene un c\u00f3digo de autorizaci\u00f3n para su propia cuenta de proveedor, luego induce a la v\u00edctima a visitar el punto final de devoluci\u00f3n de llamada con ese c\u00f3digo y sin par\u00e1metro de estado. La aplicaci\u00f3n inicia la sesi\u00f3n de la v\u00edctima como el atacante, por lo que las acciones posteriores de la v\u00edctima ocurren en la cuenta del atacante donde el atacante puede leerlas. Las aplicaciones que reutilizan una devoluci\u00f3n de llamada tanto para iniciar sesi\u00f3n como para vincular una cuenta de proveedor est\u00e1n a\u00fan m\u00e1s expuestas a la toma de control de cuenta, quedando la cuenta del atacante vinculada a la v\u00edctima.\n\nLa alternativa permisiva no sirve a ning\u00fan flujo conforme. El inicio de sesi\u00f3n iniciado por terceros llega a una parte confiable en un punto final de inicio de sesi\u00f3n separado y hace que env\u00ede una nueva petici\u00f3n de autenticaci\u00f3n, y esta biblioteca no implementa tal punto final. Oidcc.Plug.Authorize siempre env\u00eda un par\u00e1metro de estado, que un servidor de autorizaci\u00f3n debe hacer eco, por lo que ninguna devoluci\u00f3n de llamada leg\u00edtima carece de uno.\n\nEste problema afecta a oidcc_plug: desde 0.2.0-beta.1 antes de 0.5.0."}], "lastModified": "2026-10-23T23:10:00.157", "sourceIdentifier": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db"}