OpenID Connect nonce generated but never validated — ID token replay attack

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

5.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P · score source

EPSS

• CVE-2026-42206: 0.15% estimated exploitation activity in the next 30 days; percentile 4.40 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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: 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…

Published by the source

29 Apr 2026, 20:51 UTC

Last modified by the source

13 May 2026, 13:38 UTC

Source last checked

26 Oct 2026, 14:40 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3gx8-q682-38mx

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-42206

Advisory: OpenID Connect nonce generated but never validated — ID token replay attack
IDs: CVE-2026-42206, GHSA-3gx8-q682-38mx
Record: https://patchnext.com/advisories/cve-2026-42206 (revision 1, source checked 26 Oct 2026, 14:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: roadiz/openid 2.7.18, 2.6.31, 2.5.45, 2.3.43. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist roadiz/openid: affected >= 2.7.0, < 2.7.18; >= 2.6.0, < 2.6.31; >= 2.5.0, < 2.5.45; < 2.3.43; fixed in 2.6.31, 2.7.18, 2.5.45, 2.3.43

## Suggested inspection (read-only)
- Packagist roadiz/openid: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on roadiz/openid.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-3gx8-q682-38mx (GitHub-reviewed advisory GHSA-3gx8-q682-38mx lists affected ranges: Packagist roadiz/openid >=2.7.0 =2.6.0 =2.5.0 =0 <2.3.43)

Commands are suggestions: review each one before running it.