CVE-2026-45363

{"id": "CVE-2026-45363", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-45363", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "yes"}, {"technicalImpact": "total"}], "version": "2.0.3", "timestamp": "2026-07-15T13:24:12.081532Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 9.1, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.2, "exploitabilityScore": 3.9}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "jwt", "product": "ruby-jwt", "versions": [{"status": "affected", "version": "< 2.10.3"}, {"status": "affected", "version": ">= 3.0.0, < 3.2.0"}]}]}], "published": "2026-07-14T22:16:54.463", "references": [{"url": "https://github.com/jwt/ruby-jwt/commit/9820020869ad147b941e49d96ab8beba35532964", "source": "security-advisories@github.com"}, {"url": "https://github.com/jwt/ruby-jwt/commit/db560b769a07bd9724e77ff505011ac01872106f", "source": "security-advisories@github.com"}, {"url": "https://github.com/jwt/ruby-jwt/releases/tag/v2.10.3", "source": "security-advisories@github.com"}, {"url": "https://github.com/jwt/ruby-jwt/releases/tag/v3.2.0", "source": "security-advisories@github.com"}, {"url": "https://github.com/jwt/ruby-jwt/security/advisories/GHSA-c32j-vqhx-rx3x", "source": "security-advisories@github.com"}, {"url": "https://lists.debian.org/debian-lts-announce/2026/09/msg00022.html", "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-287"}, {"lang": "en", "value": "CWE-326"}, {"lang": "en", "value": "CWE-1391"}]}], "descriptions": [{"lang": "en", "value": "ruby-jwt is a Ruby implementation of the RFC 7519 OAuth JSON Web Token standard. Prior to 2.10.3 and 3.2.0, JWT.decode(token, '', true, algorithm: 'HS256') accepts an attacker-forged token because OpenSSL::HMAC.digest('SHA256', '', payload) returns a valid digest under an empty key and no empty-key precondition exists in the HMAC algorithm. The same path is reached when a keyfinder block or key_finder: argument returns an empty string, nil, or an array containing nil for an unknown key, affecting HS256, HS384, and HS512 verification through JWT.decode and JWT::EncodedToken#verify_signature!. This issue is fixed in versions 2.10.3 and 3.2.0."}, {"lang": "es", "value": "ruby-jwt es una implementaci\u00f3n en Ruby del est\u00e1ndar RFC 7519 OAuth JSON Web Token. Antes de las versiones 2.10.3 y 3.2.0, JWT.decode(token, \u2019\u2019, true, algorithm: \u2019HS256\u2019) acepta un token forjado por un atacante porque OpenSSL::HMAC.digest(\u2019SHA256\u2019, \u2019\u2019, payload) devuelve un digest v\u00e1lido con una clave vac\u00eda y no existe ninguna precondici\u00f3n de clave vac\u00eda en el algoritmo HMAC. Se alcanza la misma ruta cuando un bloque keyfinder o un argumento key_finder: devuelve una cadena vac\u00eda, nil, o un array que contiene nil para una clave desconocida, afectando la verificaci\u00f3n de HS256, HS384 y HS512 a trav\u00e9s de JWT.decode y JWT::EncodedToken#verify_signature!. Este problema est\u00e1 solucionado en las versiones 2.10.3 y 3.2.0."}], "lastModified": "2026-10-24T22:10:00.210", "sourceIdentifier": "security-advisories@github.com"}