{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-18092 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-18092 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-18092 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, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-18092 and fix it if it is affected.\n\nWhat it is: CVE-2026-18092 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, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-18092 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-18092/ (Markdown: https://insights.sbomify.com/CVE-2026-18092/index.md)","id":"CVE-2026-18092","markdown":"https://insights.sbomify.com/CVE-2026-18092/index.md","name":"CVE-2026-18092","record":{"aliases":["GHSA-657v-xpf8-79x2"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Perl SAML library","requires_auth":"none","summary":"Attackers can bypass SAML authentication and impersonate arbitrary users by exploiting XML signature wrapping in the Net::SAML2 Perl library.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CPANSec","cpe":[{"product":"net\\","vendor":"timlegge"}],"cvss":{"score":8.1,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"Net::SAML2 versions before 0.86 for Perl allow SAML authentication bypass via XML signature wrapping because new_from_xml reads assertion identity with document-wide XPath instead of the signed subtree.\n\nnew_from_xml reads the NameID, attribute values, SessionIndex, audience and other identity fields with document-wide XPath, such as //saml:Assertion/saml:AttributeStatement/saml:Attribute and //saml:Subject/saml:NameID, which select the first matching element in document order rather than the element covered by the verified signature. handle_response confirms that a signature is present and, when a cacert is configured, that it chains to the CA, but XML::Sig verifies only the element named by the signature's Reference URI, so unsigned sibling assertions in the same document are not covered. An attacker who holds any one IdP-signed assertion can add an unsigned attacker-authored assertion earlier in document order; the signature still verifies and the document-order XPath returns the attacker's NameID and attributes.\n\nAny caller that passes an untrusted Response to new_from_xml can accept identity fields from an assertion the IdP never signed, even when a cacert trust anchor is configured, so a party holding one valid IdP-signed assertion can authenticate as an arbitrary user.","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-18092","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"IBM Financial Transaction Manager (FTM) is Impacted by Multiple Vulnerabilities","id":"CVE-2026-18095"},"packages":[],"prev":{"headline":"Gdk-pixbuf: gdk-pixbuf: heap out-of-bounds read in uncompress() via crafted icns rle block","id":"CVE-2026-18090"},"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":7.5,"headline":"Auth bypass in Net::SAML2","id":"CVE-2026-18089","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-03","vendors":["TIMLEGGE"]},"summary":"Attackers can bypass SAML authentication and impersonate arbitrary users by exploiting XML signature wrapping in the Net::SAML2 Perl library.","url":"https://insights.sbomify.com/CVE-2026-18092/"}