{"answers":{"affected":"2 open source packages ship an affected version, including relyra.","exploited":"There is no known exploitation of CVE-2026-49454 in the wild and no public exploit code.","fix":"Upgrade relyra to 1.2.0 or later.","what":"CVE-2026-49454 is a critical authentication bypass vulnerability in szTheory relyra, published on 18 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-49454 and fix it if it is affected.\n\nWhat it is: CVE-2026-49454 is a critical authentication bypass vulnerability in szTheory relyra, published on 18 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-49454 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- relyra (Hex): affected from 1.0.0; fixed in 1.2.0\n- relyra (Hex): affected from 1.0.0; fixed in 1.2.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-49454/ (Markdown: https://insights.sbomify.com/CVE-2026-49454/index.md)","id":"CVE-2026-49454","markdown":"https://insights.sbomify.com/CVE-2026-49454/index.md","name":"CVE-2026-49454","record":{"aliases":["GHSA-jv46-xfwm-36j7"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Elixir SAML library","requires_auth":"none","summary":"Attackers can bypass authentication in Relyra SAML library by forging signatures, allowing unauthorized access and account takeover.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"},{"id":"CWE-287","name":"Improper Authentication"}],"description":"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.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Relyra SAML SignatureValue not cryptographically verified -\u003e authentication bypass","id":"CVE-2026-49454","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Waku: Cross-Origin CSRF on RSC Server Action Dispatch","id":"CVE-2026-49455"},"packages":[{"ecosystem":"Hex","fixed":["1.2.0"],"introduced":["1.0.0"],"last_affected":[],"package":"relyra","purl":null,"source":"GHSA-jv46-xfwm-36j7"},{"ecosystem":"Hex","fixed":["1.2.0"],"introduced":["1.0.0"],"last_affected":[],"package":"relyra","purl":"pkg:hex/relyra","source":"GHSA-jv46-xfwm-36j7"}],"prev":{"headline":"Joplin: Path traversal in resource sync — silent arbitrary file write outside the resource directory","id":"CVE-2026-49453"},"products":["relyra"],"published":"2026-06-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-22","vendors":["szTheory"]},"summary":"Attackers can bypass authentication in Relyra SAML library by forging signatures, allowing unauthorized access and account takeover.","url":"https://insights.sbomify.com/CVE-2026-49454/"}