{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-3255 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-3255 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-3255 is a medium-severity vulnerability in TOKUHIROM HTTP::Session2, published on 27 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-3255 and fix it if it is affected.\n\nWhat it is: CVE-2026-3255 is a medium-severity vulnerability in TOKUHIROM HTTP::Session2, published on 27 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-3255 in the wild and no public exploit code.\n\nAffected product: TOKUHIROM HTTP::Session2. 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-3255/ (Markdown: https://insights.sbomify.com/CVE-2026-3255/index.md)","id":"CVE-2026-3255","markdown":"https://insights.sbomify.com/CVE-2026-3255/index.md","name":"CVE-2026-3255","record":{"aliases":["GHSA-2p7f-7xjf-8q9q"],"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 number generation, potentially leading to account takeover.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CPANSec","cpe":[{"product":"http\\","vendor":"tokuhirom"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L","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::Session2 versions before 1.12 for Perl for Perl may generate weak session ids using the rand() function.\n\nThe HTTP::Session2 session id generator returns a SHA-1 hash seeded with the built-in rand function, the 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\nHTTP::Session2 after version 1.02 will attempt to use the /dev/urandom device to generate a session id, but if the device is unavailable (for example, under Windows), then it will revert to the insecure method described above.","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::Session2 versions before 1.12 for Perl may generate weak session ids using the rand() function","id":"CVE-2026-3255","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":"HTTP::Session versions before 0.54 for Perl defaults to using insecurely generated session ids","id":"CVE-2026-3256"},"packages":[],"prev":{"headline":"Improper Restriction of Rendered UI Layers or Frames in GitLab","id":"CVE-2026-3254"},"products":["HTTP::Session2"],"published":"2026-02-27","related":[{"cvss_score":6.5,"headline":"Code injection in HTTP::Session2","id":"CVE-2018-25160","kev_date_added":null,"published":"2026-02-27"}],"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-03-03","vendors":["TOKUHIROM"]},"summary":"Attackers can predict session IDs due to weak random number generation, potentially leading to account takeover.","url":"https://insights.sbomify.com/CVE-2026-3255/"}