{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-2439 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-2439 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-2439 is a critical vulnerability in BVA Concierge::Sessions, published on 16 Feb 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-2439 and fix it if it is affected.\n\nWhat it is: CVE-2026-2439 is a critical vulnerability in BVA Concierge::Sessions, published on 16 Feb 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-2439 in the wild and no public exploit code.\n\nAffected product: BVA Concierge::Sessions. 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-2439/ (Markdown: https://insights.sbomify.com/CVE-2026-2439/index.md)","id":"CVE-2026-2439","markdown":"https://insights.sbomify.com/CVE-2026-2439/index.md","name":"CVE-2026-2439","record":{"aliases":["GHSA-9gww-cr64-679c"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Perl session library","requires_auth":"none","summary":"Attackers can guess insecure session IDs generated by the Concierge::Sessions Perl library, leading to unauthorized access and account takeover.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CPANSec","cpe":[{"product":"concierge\\","vendor":"bva"}],"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-340","name":"Generation of Predictable Numbers or Identifiers"},{"id":"CWE-338","name":"Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)"}],"description":"Concierge::Sessions versions from 0.8.1 before 0.8.5 for Perl generate insecure session ids. The generate_session_id function in Concierge::Sessions::Base defaults to using the uuidgen command to generate a UUID, with a fallback to using Perl's built-in rand function. Neither of these methods are secure, and attackers are able to guess session_ids that can grant them access to systems. Specifically,\n\n  *  There is no warning when uuidgen fails. The software can be quietly using the fallback rand() function with no warnings if the command fails for any reason.\n  *  The uuidgen command will generate a time-based UUID if the system does not have a high-quality random number source, because the call does not explicitly specify the --random option. Note that the system time is shared in HTTP responses.\n  *  UUIDs are identifiers whose mere possession grants access, as per RFC 9562.\n  *  The output of the built-in rand() function is predictable and unsuitable for security applications.","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":"Concierge::Sessions versions from 0.8.1 before 0.8.5 for Perl generate insecure session ids","id":"CVE-2026-2439","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"SurveyJS: Drag \u0026 Drop Form Builder \u003c= 2.5.3 - Unauthenticated Stored Cross-Site Scripting","id":"CVE-2026-2440"},"packages":[],"prev":{"headline":"Cross-site scripting in WP Travel Engine – Tour Booking Plugin – Tour Operator Software","id":"CVE-2026-2437"},"products":["Concierge::Sessions"],"published":"2026-02-16","related":[],"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-02-17","vendors":["BVA"]},"summary":"Attackers can guess insecure session IDs generated by the Concierge::Sessions Perl library, leading to unauthorized access and account takeover.","url":"https://insights.sbomify.com/CVE-2026-2439/"}