CVE-2026-5085
Mcrawfor Solstice\ \
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NSummary
CVE-2026-5085 is a critical-severity PRNG (CWE-338) vulnerability in Mcrawfor Solstice\. Its CVSS base score is 9.1 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Forge Web Credentials (T1606); ranked at the 27th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SC-12 (Cryptographic Key Establishment and Management) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-5085 affects Solstice::Session versions through 1440 for Perl, where the _generateSessionID method insecurely generates session IDs as an MD5 digest seeded by low-entropy inputs: the epoch time, a random hash reference, the built-in rand() function, and the process ID. The same flawed method appears in the _generateID method of Solstice::Subsession, part of the same distribution. These inputs are predictable—epoch time can be guessed unless leaked via the HTTP Date header, stringified hash references contain foreseeable content, rand() uses only a 16-bit seed unsuitable for security, and process IDs draw from a limited range—leading to session IDs that lack sufficient randomness.
Remote attackers require no privileges or user interaction to exploit this over the network with low complexity, as indicated by the CVSS 3.1 score of 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N). By predicting session IDs (CWE-338: predictable values; CWE-340: generation with insufficient entropy), they can hijack active sessions and gain unauthorized access to affected systems.
Advisories, including the OSS-security mailing list disclosure and MetaCPAN's security guide on random data, highlight the need for cryptographically secure randomness in session generation, pointing to the vulnerable source code in Solstice::Session.pm and Solstice::Subsession.pm. No patches are detailed in the provided references.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-21885
Vulnerability Data
Solstice::Session versions through 1440 for Perl generates session ids insecurely. The _generateSessionID method returns an MD5 digest seeded by the epoch time, a random hash reference, a call to the built-in rand() function and the process id. The same method…
more
is used in the _generateID method in Solstice::Subsession, which is part of the same distribution. The epoch time may be guessed, if it is not leaked in the HTTP Date header. Stringified hash refences will contain predictable content. The built-in rand() function is seeded by 16-bits and is unsuitable for security purposes. The process id comes from a small set of numbers. Predictable session ids could allow an attacker to gain access to systems.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 9 hardening rules · 4 OS baselines
V7.2.3V11.5.1V11.3.4
Mitigating Controls (NIST 800-53 r5) AI
Requiring specific approved cryptography for protection directly mandates use of strong PRNGs instead of weak ones.
Developer testing and evaluation can discover predictable number generation through targeted analysis or fuzzing of identifier creation routines.
Cryptographic key establishment and management mandates proper entropy and randomness during generation, directly stopping predictable identifiers at the source.
Authenticator management requires secure initial distribution and handling of authenticators, structurally preventing predictable values from being usable.
Engineering principles applied during design and development include selection of cryptographically strong random number generation.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices explicitly require cryptographically strong RNG selection and usage in security contexts.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Mandates use of approved cryptographic controls, directly requiring cryptographically strong RNGs.
Security testing can detect use of weak random number generators.
Secure SDLC processes should catch weak PRNG usage during design and code review.
Application security requirements can specify cryptographically strong random number generation.
Secure engineering principles include selection of appropriate cryptographic primitives.
Secure coding standards prohibit use of weak PRNGs in security contexts.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (3 rules)
- V-248524 OL 8 must implement NIST FIPS-validated cryptography for the following: To provision digital signatures, to generate cryptographic hashes, and to protect data requiring data-at-rest protections in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. prevents CWE-340
- V-248563 The OL 8 SSH server must be configured to use strong entropy. prevents CWE-338
- V-248600 OL 8 must have the packages required to use the hardware random number generator entropy gatherer service. prevents CWE-340
RHEL 7 (1 rule)
- V-204497 The Red Hat Enterprise Linux operating system must implement NIST FIPS-validated cryptography for the following: to provision digital signatures, to generate cryptographic hashes, and to protect data requiring data-at-rest protections in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. prevents CWE-340
RHEL 8 (2 rules)
- V-230253 RHEL 8 must ensure the SSH server uses strong entropy. prevents CWE-338
- V-244527 RHEL 8 must have the packages required to use the hardware random number generator entropy gatherer service. prevents CWE-340
Ubuntu 22.04 (1 rule)
- V-260650 Ubuntu 22.04 LTS must implement NIST FIPS-validated cryptography to protect classified information and for the following: To provision digital signatures, to generate cryptographic hashes, and to protect unclassified information requiring confidentiality and cryptographic protection in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. prevents CWE-338