← Back
CVE-2026-49454
critical
CVSS 9.1
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**authentication bypass** (CWE-287) exists in relyra. Attackers reach the vulnerable code path via ``SignatureValue`` without authentication.
📍 Affected scope
relyra — . Attack surface: `SignatureValue` / `SignedInfo` / `DigestValue` / `NameID`.
🔥 Severity
Severity: Critical (CVSS 9.1/10). Confidential information can be exposed externally
🔧 How to fix
Update to **1.2.0**.
🛡️ Workaround
Workaround: There is no safe configuration of `1.0.0` or `1.1.0`.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
There is no safe configuration of `1.0.0` or `1.1.0`.パッチが適用されるまでの応急処置として、There is no safe configuration of `1.0.0` or `1.1.0`. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade relyra to 1.2.0ステージング環境で 1.2.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
erlang
relyra
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.2.0"}]}]
References
- web https://github.com/szTheory/relyra/commit/2e456897af3158c175bb490ce7fc51d6241c8922
- web https://github.com/szTheory/relyra/commit/8910200
- web https://github.com/szTheory/relyra/security/advisories/GHSA-jv46-xfwm-36j7
- web https://nvd.nist.gov/vuln/detail/CVE-2026-49454
- web https://github.com/advisories/GHSA-jv46-xfwm-36j7