Authentication Bypass in relyra (CVE-2026-49454)
Summary
Authentication bypass in relyra (CVE-2026-49454). Confidential information can be exposed externally. Exploitable via SignatureValue. Mitigation: upgrade to 1.2.0 or later.
Original description
The description as published by the source.
Relyra is a strict-by-default SAML 2.0 Service Provider library for Elixir and Phoenix. Versions 1.0.0 and 1.1.0 accept forged SAML signatures because SignatureValue was not cryptographically verified before the library returned a successful authentication result. The XMLDSig trust boundary was incomplete as :public_key.verify over the exclusive-C14N canonicalized SignedInfo was not performed against the configured IdP certificate's public key, DigestValue was not recomputed over the canonicalized referenced element, and canonicalize/2 remained an unused passthrough in the signature-verification path. The result was a structure-only acceptance path where document shape and trust-source rejection could succeed without proving the signature bytes. A forged SignatureValue carrying an attacker-controlled NameID could be accepted as {:ok}. This issue has been fixed in version 1.2.0.
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-49454 has been found in relyra.
Attackers can target a specific entry point like SignatureValue over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.1/10.
What to do: upgrade relyra to 1.2.0 or later.
If unsure, ask your IT team or search "relyra CVE-2026-49454" on the vendor's site.
CVE-2026-49454 (relyra) — CWE-287 / CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: SignatureValue / SignedInfo / DigestValue / NameID
Patched: 1.2.0 — apply immediately
Workaround: There is no safe configuration of 1.0.0 or 1.1.0.
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.
Authentication bypass (CWE-287) exists in relyra. Attackers reach the vulnerable code path via SignatureValue without authentication.
Check the vendor advisory for the affected versions of relyra. Attack surface: SignatureValue / SignedInfo / DigestValue / NameID.
Severity: Critical (CVSS 9.1/10). Confidential information can be exposed externally.
Update to 1.2.0.
Workaround: There is no safe configuration of 1.0.0 or 1.1.0.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'relyra' . 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 'relyra' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
relyraを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
There is no safe configuration of `1.0.0` or `1.1.0`.パッチが適用されるまでの応急処置として、There is no safe configuration of
1.0.0or1.1.0. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade relyra to 1.2.0ステージング環境で 1.2.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-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
- patch github.com
- patch github.com
- web github.com