{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-18108 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-18108 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-18108 is a critical 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-18108 and fix it if it is affected.\n\nWhat it is: CVE-2026-18108 is a critical 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-18108 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-18108/ (Markdown: https://insights.sbomify.com/CVE-2026-18108/index.md)","id":"CVE-2026-18108","markdown":"https://insights.sbomify.com/CVE-2026-18108/index.md","name":"CVE-2026-18108","record":{"aliases":["GHSA-g48m-j5m7-625h"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Perl SAML2 library","requires_auth":"none","summary":"Attackers can bypass authentication in Perl SAML2 libraries by sending unsigned encrypted assertions, allowing them to impersonate arbitrary users.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CPANSec","cpe":[{"product":"net\\","vendor":"timlegge"}],"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":"Net::SAML2 versions before 0.86 for Perl allow authentication bypass because _verify_encrypted_assertion accepts an EncryptedAssertion whose decrypted content carries no signature.\n\n_verify_encrypted_assertion decrypts the EncryptedAssertion and returns it as verified when it carries no signature, via \"return $xml unless $xpath-\u003eexists('dsig:Signature', $assert);\". The signature check and the trust anchor check that follow run only when a signature is present, so a decrypted assertion with no dsig:Signature element reaches new_from_xml unverified and its NameID and attributes are read into the assertion object. An SP's encryption certificate is published in its SAML metadata so the IdP can encrypt to it, so any party can encrypt an unsigned assertion to that certificate, wrap it in a samlp:Response, and post it to the assertion consumer service.\n\nAny caller that configures a decryption key_file, and so accepts EncryptedAssertions, takes identity fields from an assertion that no trust anchor covers, and an unauthenticated party can authenticate as an arbitrary user. Callers with no key_file configured do not decrypt and are unaffected.","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-18108","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":"W3 Total Cache \u003c= 2.10.3 - Unauthenticated Stored Cross-Site Scripting via Comment Author Name","id":"CVE-2026-18109"},"packages":[],"prev":{"headline":"Criu: criu: container escape via rseq critical section hijack during checkpoint/restore","id":"CVE-2026-18107"},"products":["Net::SAML2"],"published":"2026-08-03","related":[{"cvss_score":8.1,"headline":"Auth bypass in Net::SAML2","id":"CVE-2026-18092","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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-03","vendors":["TIMLEGGE"]},"summary":"Attackers can bypass authentication in Perl SAML2 libraries by sending unsigned encrypted assertions, allowing them to impersonate arbitrary users.","url":"https://insights.sbomify.com/CVE-2026-18108/"}