roadiz/openid
Affected
- introduced
2.7.0, fixed2.7.18(ecosystem)
Fixed versions
2.7.18
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-42206
OpenID Connect nonce generated but never validated — ID token replay attack
Summary
The roadiz/openid package generates an OIDC nonce in OAuth2LinkGenerator::generate() and includes it in the authorization request sent to the identity provider, but never stores it and never validates it on the callback. The OpenIdJwtConfigurationFactory validation chain does not include a nonce constraint, and OpenIdAuthenticator::authenticate() never checks the nonce claim in the returned ID token against a stored value.
Details
In src/OAuth2LinkGenerator.php, a nonce is created and sent to the IdP:
'nonce' => $this->tokenGenerator->generateToken(),
However, this value is neither stored in session, cache, nor any other persistent store.
In src/OpenIdJwtConfigurationFactory.php, the JWT validation constraints are:
LooseValidAt (expiry)PermittedFor (audience)IssuedBy (issuer)HostedDomain (optional)UserInfoEndpoint (optional)No nonce constraint is present.
In src/Authentication/OpenIdAuthenticator.php, the authenticate() method validates the state CSRF token correctly (fixed in v2.7.10), but never retrieves a stored nonce or compares it against the nonce claim in the ID token.
PoC
Additionally, in an authorization code flow with multiple concurrent sessions, a malicious IdP or a compromised token endpoint could inject a token with a mismatched nonce, and the application would accept it silently.
Impact
roadiz/openid package with OpenID Connect SSO.The OIDC Core 1.0 specification (Section 3.1.3.7) explicitly requires clients to verify the nonce claim if it was present in the authorization request.
Medium Basis: The source's own band: MODERATE
2.7.0, fixed 2.7.18 (ecosystem)2.7.18
The export has no generic command for this ecosystem.
2.6.0, fixed 2.6.31 (ecosystem)2.6.31
The export has no generic command for this ecosystem.
2.5.0, fixed 2.5.45 (ecosystem)2.5.45
The export has no generic command for this ecosystem.
0, fixed 2.3.43 (ecosystem)2.3.43
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0