253067 matches found
MINI-HCXH-P8R5-JCV6
Bulletin has no description...
MINI-5GFC-R5JC-3Q29
Bulletin has no description...
MINI-Q282-2W85-3WMQ
Bulletin has no description...
MINI-V24P-29Q3-6XJP
Bulletin has no description...
MINI-6H8P-66QM-879X
Bulletin has no description...
MINI-JH99-9722-7GG6
Bulletin has no description...
MINI-Q8F6-JC6X-9R9H
Bulletin has no description...
MINI-43PJ-9QVQ-HHR5
Bulletin has no description...
MINI-H9F2-4VGF-6832
Bulletin has no description...
MINI-PGCH-FF37-R9QQ
Bulletin has no description...
MINI-XF64-32J2-G7CV
Bulletin has no description...
MINI-X57H-5686-4CJP
Bulletin has no description...
MINI-X5F2-PCQ2-HF3H
Bulletin has no description...
MINI-PHFW-96XM-7673
Bulletin has no description...
MINI-PX44-3FPJ-M7HM
Bulletin has no description...
MINI-9JF9-WQJM-R6H5
Bulletin has no description...
MINI-JR82-25RC-7JF4
Bulletin has no description...
ECHO-1969-C688-A45C Keycloak's GHSA advisory (GHSA-rr5q-3xwr-f323) lists the affected range as < 26.6.3 with no lower bound, so by version string alone 25.0.6 is nominally in range. The actual vulnerability requires a generic parameter-length-limiting mechanism (OIDCProviderConfig's max-length-per-parameter config, TokenEndpoint's checkParameters() gate) that silently drops any oversized request parameter, including subject_token — the fix exempts token-shaped parameters from that drop via a new getTokenParameterNames() method. That length-limiting framework does not exist anywhere in 25.0.6 (same finding as CVE-2026-4634, investigated separately) — confirmed via source search, no getMaxLengthForTheParameter/checkParameters/length-cap mechanism exists on any OIDC grant-type endpoint. With no mechanism to silently drop an oversized subject_token, the described fallback to client-credentials cannot occur.
Bulletin has no description...