{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-3256 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-3256 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-3256 is a critical vulnerability in KTAT HTTP::Session, published on 28 Mar 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-3256 and fix it if it is affected.\n\nWhat it is: CVE-2026-3256 is a critical vulnerability in KTAT HTTP::Session, published on 28 Mar 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-3256 in the wild and no public exploit code.\n\nAffected product: KTAT HTTP::Session. 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-3256/ (Markdown: https://insights.sbomify.com/CVE-2026-3256/index.md)","id":"CVE-2026-3256","markdown":"https://insights.sbomify.com/CVE-2026-3256/index.md","name":"CVE-2026-3256","record":{"aliases":["GHSA-mx9c-4xjq-mhj6"],"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 predict session IDs due to weak random seeding, potentially leading to account takeover in applications using this Perl library.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CPANSec","cpe":[{"product":"http\\","vendor":"ktat"}],"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":"HTTP::Session versions before 0.54 for Perl defaults to using insecurely generated session ids.\n\nHTTP::Session defaults to using HTTP::Session::ID::SHA1 to generate session ids using a SHA-1 hash seeded with the built-in rand function, the high resolution epoch time, and the PID. The PID will come from a small set of numbers, and the epoch time may be guessed, if it is not leaked from the HTTP Date header. The built-in rand function is unsuitable for cryptographic usage.\n\nThe distribution includes HTTP::session::ID::MD5 which contains a similar flaw, but uses the MD5 hash instead.","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":"HTTP::Session versions before 0.54 for Perl defaults to using insecurely generated session ids","id":"CVE-2026-3256","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"UnQLite versions through 0.06 for Perl uses a potentially insecure version of the UnQLite library","id":"CVE-2026-3257"},"packages":[],"prev":{"headline":"HTTP::Session2 versions before 1.12 for Perl may generate weak session ids using the rand() function","id":"CVE-2026-3255"},"products":["HTTP::Session"],"published":"2026-03-28","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-06-29","vendors":["KTAT"]},"summary":"Attackers can predict session IDs due to weak random seeding, potentially leading to account takeover in applications using this Perl library.","url":"https://insights.sbomify.com/CVE-2026-3256/"}