What is CVE-2026-49454?

CVE-2026-49454 is a critical-severity improper authentication vulnerability in relyra (erlang), affecting versions >= 1.0.0, < 1.2.0. It is fixed in 1.2.0. The application does not adequately verify the identity of a user, device, or process before granting access.

How severe is CVE-2026-49454?

CVE-2026-49454 has a CVSS score of 9.1 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of relyra are affected by CVE-2026-49454?

relyra (erlang) versions >= 1.0.0, < 1.2.0 is affected.

Is there a fix for CVE-2026-49454?

Yes. CVE-2026-49454 is fixed in 1.2.0. Upgrade to this version or later.

Is CVE-2026-49454 exploitable, and should I be worried?

Whether CVE-2026-49454 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-49454 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-49454?

Upgrade relyra to 1.2.0 or later.

CVE-2026-49454 in relyra

Q: How severe is CVE-2026-49454?

CVE-2026-49454 has a CVSS score of 9.1 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of relyra are affected by CVE-2026-49454?

relyra (erlang) versions >= 1.0.0, < 1.2.0 is affected.

Q: Is there a fix for CVE-2026-49454?

Yes. CVE-2026-49454 is fixed in 1.2.0. Upgrade to this version or later.

Q: Is CVE-2026-49454 exploitable, and should I be worried?

Whether CVE-2026-49454 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-49454 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-49454?

Upgrade relyra to 1.2.0 or later.

Summary

Relyra SAML SignatureValue not cryptographically verified -> authentication bypass

Relyra 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.

Details

In 1.0.0 and 1.1.0, the XMLDSig trust boundary was incomplete. :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.

Workarounds

There is no safe configuration of 1.0.0 or 1.1.0. Upgrade to 1.2.0 or later.

Resources

Fix commit 2e45689 (wire real XMLDSig crypto into the candidate arm)
Fix commit 8910200 (close metadata trust bypass, pin over DER)
Regression proof: test/security/xml/adversarial_crypto_test.exs, test/relyra/metadata/auto_refresh_test.exs, test/security/ci_gate_integrity_test.exs

Impact

A forged SignatureValue carrying an attacker-controlled NameID can be accepted as {:ok}. Any relying-party application using Relyra 1.0.0 or 1.1.0 can be logged into as an arbitrary user if it trusts the affected response path.

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

CVE-2026-49454 has a CVSS score of 9.1 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.2.0); upgrading removes the vulnerable code path.

Affected versions

relyra (>= 1.0.0, < 1.2.0)

Security releases

relyra → 1.2.0 (erlang)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Relyra 1.2.0 closes the gap with real exclusive-C14N canonicalization, :public_key.verify against the configured IdP certificate's public key, and a constant-time DigestValue recompute/compare bound to the exact consumed node on both verify/4 and verify_metadata_root/4.

Frequently Asked Questions

What is CVE-2026-49454? CVE-2026-49454 is a critical-severity improper authentication vulnerability in relyra (erlang), affecting versions >= 1.0.0, < 1.2.0. It is fixed in 1.2.0. The application does not adequately verify the identity of a user, device, or process before granting access.
How severe is CVE-2026-49454? CVE-2026-49454 has a CVSS score of 9.1 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of relyra are affected by CVE-2026-49454? relyra (erlang) versions >= 1.0.0, < 1.2.0 is affected.
Is there a fix for CVE-2026-49454? Yes. CVE-2026-49454 is fixed in 1.2.0. Upgrade to this version or later.
Is CVE-2026-49454 exploitable, and should I be worried? Whether CVE-2026-49454 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-49454 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-49454? Upgrade relyra to 1.2.0 or later.