Vulnerability in roadiz/openid (CVE-2026-42206)
Summary
Vulnerability in roadiz/openid (CVE-2026-42206). Risk of unauthorized operations or information disclosure. Exploitable via OpenIdJwtConfigurationFactory. Mitigation: upgrade to 2.7.10 or later.
Original description
The description as published by the source.
Roadiz is a polymorphic content management system based on a node system. Prior to versions 2.3.43, 2.5.45, 2.6.31, and 2.7.18, 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. This issue has been patched in versions 2.3.43, 2.5.45, 2.6.31, and 2.7.18.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-42206 has been found in roadiz/openid.
Attackers can target a specific entry point like OpenIdJwtConfigurationFactory over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade roadiz/openid to 2.7.10 or later.
If unsure, ask your IT team or search "roadiz/openid CVE-2026-42206" on the vendor's site.
CVE-2026-42206 (roadiz/openid) — CWE-345
Attack surface: OpenIdJwtConfigurationFactory / LooseValidAt / PermittedFor / IssuedBy
Patched: 2.7.10 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-345) exists in roadiz/openid. Attackers reach the vulnerable code path via OpenIdJwtConfigurationFactory.
Check the vendor advisory for the affected versions of roadiz/openid. Attack surface: OpenIdJwtConfigurationFactory / LooseValidAt / PermittedFor / IssuedBy.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.7.10.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'roadiz/openid' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'roadiz/openid' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
roadiz/openidを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade roadiz/openid to 2.7.10ステージング環境で 2.7.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com