Lucene search
+L

10 matches found

CVE
CVE
•added 2026/08/18 6:49 p.m.•55 views

CVE-2026-55165

In Lemur 1.9.0 and earlier, lemur/auth/service.py:130-137 reads the alg field from an unverified JWT header and passes it to pyjwt.decode(..., algorithms=[header_data["alg"]]), letting an attacker choose the verification algorithm. PyJWT 2.x blocks alg=none, so direct ATO requires a separate LEMU...

4.8CVSS5.9AI score0.00154EPSS
SaveExploits0References3
Vulnrichment
Vulnrichment
•added 2026/08/18 6:49 p.m.•15 views

CVE-2026-55165 Lemur : JWT verifier trusts attacker-supplied alg from token header — defense-in-depth gap; chain-dependent ATO with secret disclosure

Lemur manages TLS certificate creation. Prior to 1.9.2, the JWT verifier in lemur/auth/service.py:130-137 used fetchtokenheader to read headerdata"alg" from an unverified token and passed that attacker-controlled value to decodewithmultiplesecrets. PyJWT 2.x rejects alg=none with the configured...

4.8CVSS5.9AI score0.00154EPSS
SaveExploits0References3
EUVD
EUVD
•added 2026/08/18 6:49 p.m.•14 views

EUVD-2026-61146

Lemur manages TLS certificate creation. Prior to 1.9.2, the JWT verifier in lemur/auth/service.py:130-137 used fetchtokenheader to read headerdata"alg" from an unverified token and passed that attacker-controlled value to decodewithmultiplesecrets. PyJWT 2.x rejects alg=none with the configured...

4.8CVSS5.3AI score0.00154EPSS
SaveExploits0References3
Cvelist
Cvelist
•added 2026/07/22 8:31 p.m.•56 views

CVE-2026-13089 OIDC::Lite versions through 0.12.1 for Perl allow ID Token signature verification bypass via a token-controlled algorithm allowlist in verify

OIDC::Lite versions through 0.12.1 for Perl allow ID Token signature verification bypass via a token-controlled algorithm allowlist in verify. When the caller does not pin an algorithm, OIDC::Lite::Model::IDToken::verify sets $self-alg$self-header-alg from the token's own header and then calls...

0.00369EPSS
SaveExploits0References3
EUVD
EUVD
•added 2026/07/22 8:31 p.m.•19 views

EUVD-2026-47803

OIDC::Lite versions through 0.12.1 for Perl allow ID Token signature verification bypass via a token-controlled algorithm allowlist in verify. When the caller does not pin an algorithm, OIDC::Lite::Model::IDToken::verify sets $self-alg$self-header-alg from the token's own header and then calls...

5.4AI score0.00369EPSS
SaveExploits0References3
Vulnrichment
Vulnrichment
•added 2026/07/22 8:31 p.m.•15 views

CVE-2026-13089 OIDC::Lite versions through 0.12.1 for Perl allow ID Token signature verification bypass via a token-controlled algorithm allowlist in verify

OIDC::Lite versions through 0.12.1 for Perl allow ID Token signature verification bypass via a token-controlled algorithm allowlist in verify. When the caller does not pin an algorithm, OIDC::Lite::Model::IDToken::verify sets $self-alg$self-header-alg from the token's own header and then calls...

5.8AI score0.00369EPSS
SaveExploits0References3
attackerkb
attackerkb
•added 2026/07/22 8:31 p.m.•18 views

CVE-2026-13089

OIDC::Lite versions through 0.12.1 for Perl allow ID Token signature verification bypass via a token-controlled algorithm allowlist in verify. When the caller does not pin an algorithm, OIDC::Lite::Model::IDToken::verify sets $self-alg$self-header-alg from the token's own header and then calls...

5.3AI score0.00369EPSS
SaveExploits0References4
Positive Technologies
Positive Technologies
•added 2026/07/22 12:00 a.m.•31 views

PT-2026-63495

Name of the Vulnerable Software and Affected Versions OIDC::Lite versions through 0.12.1 Description An issue exists where ID Token signature verification can be bypassed due to a token-controlled algorithm allowlist in the verify function. When a caller does not specify a pinned algorithm, the...

7.5CVSS6AI score0.00369EPSS
SaveExploits0References7
Github Security Blog
Github Security Blog
•added 2026/01/13 9:52 p.m.•23 views

Hono JWK Auth Middleware has JWT algorithm confusion when JWK lacks "alg" (untrusted header.alg fallback)

Summary A flaw in Hono’s JWK/JWKS JWT verification middleware allowed the algorithm specified in the JWT header to influence signature verification when the selected JWK did not explicitly define an algorithm. This could enable JWT algorithm confusion and, in certain configurations, allow forged...

8.2CVSS5.5AI score0.00136EPSS
SaveExploits0References4Affected Software1
CVE
CVE
•added 2026/01/13 7:49 p.m.•83 views

CVE-2026-22818

CVE-2026-22818 concerns Hono’s JWK/JWKS JWT verification middleware. Prior to 4.11.4, if a JWK did not explicitly specify an algorithm, the middleware could derive the signature verification algorithm from the untrusted JWT header’s alg value, enabling algorithm confusion and potentially forged t...

8.2CVSS5.6AI score0.00136EPSS
SaveExploits0References2Affected Software1
Rows per page
Query Builder