{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-18089 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-18089 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-18089 is a high-severity authentication bypass vulnerability in TIMLEGGE Net::SAML2, published on 3 Aug 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-18089 and fix it if it is affected.\n\nWhat it is: CVE-2026-18089 is a high-severity authentication bypass vulnerability in TIMLEGGE Net::SAML2, published on 3 Aug 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-18089 in the wild and no public exploit code.\n\nAffected product: TIMLEGGE Net::SAML2. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-18089/ (Markdown: https://insights.sbomify.com/CVE-2026-18089/index.md)","id":"CVE-2026-18089","markdown":"https://insights.sbomify.com/CVE-2026-18089/index.md","name":"CVE-2026-18089","record":{"aliases":["GHSA-p5j9-p2w8-q5rw"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Perl SAML library","requires_auth":"none","summary":"Attackers can bypass SAML authentication by embedding self-signed certificates in responses when no trust anchor is configured in the Perl library.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CPANSec","cpe":[{"product":"net\\","vendor":"timlegge"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"},{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"Net::SAML2 versions before 0.86 for Perl allow SAML authentication bypass by verifying responses against the response-embedded certificate in verify_xml when no trust anchor is configured.\n\nverify_xml in Net::SAML2::Role::VerifyXML runs \"return if !$anchors \u0026\u0026 !$cacert;\" as soon as the XML::Sig check succeeds, and that check uses the X.509 certificate taken from the response's own dsig:KeyInfo/dsig:X509Certificate element, so an unanchored response is checked only against the key it carries. Binding::POST declares cacert as an optional Maybe[Str] with no default, so a POST binding built without one takes that path, and _verify_encrypted_assertion returns early the same way with \"return $xml unless $cacert;\".\n\nAny caller that constructs Binding::POST or calls Assertion-\u003enew_from_xml without a cacert, cert_text, or anchors argument accepts a response signed by an attacker generated key whose self-signed certificate is embedded in that response, authenticating an arbitrary assertion.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Auth bypass in Net::SAML2","id":"CVE-2026-18089","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Gdk-pixbuf: gdk-pixbuf: heap out-of-bounds read in uncompress() via crafted icns rle block","id":"CVE-2026-18090"},"packages":[],"prev":{"headline":"IBM i is Affected By Multiple Vulnerabilities in Java Secure Sockets Extension","id":"CVE-2026-18086"},"products":["Net::SAML2"],"published":"2026-08-03","related":[{"cvss_score":9.8,"headline":"Auth bypass in Net::SAML2","id":"CVE-2026-18108","kev_date_added":null,"published":"2026-08-03"},{"cvss_score":8.1,"headline":"Auth bypass in Net::SAML2","id":"CVE-2026-18092","kev_date_added":null,"published":"2026-08-03"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":"partial"},"state":"PUBLISHED","updated":"2026-08-03","vendors":["TIMLEGGE"]},"summary":"Attackers can bypass SAML authentication by embedding self-signed certificates in responses when no trust anchor is configured in the Perl library.","url":"https://insights.sbomify.com/CVE-2026-18089/"}