{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-86304 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-86304 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-86304 is a critical authentication bypass vulnerability, published on 6 Sep 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-86304 and fix it if it is affected.\n\nWhat it is: CVE-2026-86304 is a critical authentication bypass vulnerability, published on 6 Sep 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-86304 in the wild and no public exploit code.\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-86304/ (Markdown: https://insights.sbomify.com/CVE-2026-86304/index.md)","id":"CVE-2026-86304","markdown":"https://insights.sbomify.com/CVE-2026-86304/index.md","name":"CVE-2026-86304","record":{"aliases":["GHSA-34pg-3x4x-4vf5"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Perl SAML authentication library","requires_auth":"none","summary":"Attackers can bypass SAML authentication in MojoX::Authentication by submitting forged responses, leading to unauthorized account access.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CPANSec","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"MojoX::Authentication versions before 0.006 for Perl allow SAML authentication bypass because parse_assertion builds Net::SAML2::Binding::POST without a trust anchor.\n\nparse_assertion in MojoX::Authentication::Model::SAML2 calls Net::SAML2::Binding::POST-\u003enew with no cacert, cert_text or anchors argument, then passes the returned XML to Net::SAML2::Protocol::Assertion-\u003enew_from_xml with the IdP signing certificate as cacert. In Net::SAML2 before 0.86 that certificate guards only encrypted assertions, so the signature on an unencrypted assertion is checked against the certificate the response itself carries.\n\nAn attacker starts a SAML login, then posts a response signed with a certificate of their own. The audience, InResponseTo and timestamp checks that follow are all satisfiable by the attacker, so the response authenticates any NameID it carries.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"MojoX::Authentication versions before 0.006 for Perl allow SAML authentication bypass because parse_assertion builds Net::SAML2::Binding::PO","id":"CVE-2026-86304","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"light0011 cms Upload.class.php upload unrestricted upload","id":"CVE-2026-86305"},"packages":[],"prev":{"headline":"92181 markdown md.c lds out-of-bounds","id":"CVE-2026-86303"},"products":[],"published":"2026-09-06","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-09-08","vendors":[]},"summary":"Attackers can bypass SAML authentication in MojoX::Authentication by submitting forged responses, leading to unauthorized account access.","url":"https://insights.sbomify.com/CVE-2026-86304/"}