dbcve.org
Solstice\Application · Mcrawfor

CVE-2026-5085

CRITICAL · 9.1 CVSS v3.1 Published 2026-04-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Solstice::Session for Perl generates predictable session IDs using MD5 hashing seeded with epoch time, a stringified hash reference, the insecure rand() function (16-bit seed), and process ID. The same vulnerable _generateID method exists in Solstice::Subsession. Attackers can predict session IDs to hijack user sessions.

MitigationReplace the session ID generation with a cryptographically secure random number generator (CSPRNG) such as Bytes::Random::Secure or Crypt::PRNG, and generate session IDs with sufficient entropy (minimum 128 bits).

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Solstice\Application
Affected:= \

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Solstice::Session is installed
    Run 'perl -MSolstice::Session -e 'print $Solstice::Session::VERSION'' or check your Perl library path for Solstice/Session.pm
    Affected if The module is installed and being used for session management
  2. Locate session ID generation code
    Search your codebase for calls to Solstice::Session methods that create session IDs, particularly constructor or new() methods
    Affected if Your application uses Solstice::Session to generate session IDs for users
  3. Inspect session ID generation for MD5 usage
    Examine the Solstice::Session source code or any custom session ID generation routines for MD5 hash function usage (grep for 'MD5', 'md5', 'Digest::MD5')
    Affected if MD5 is used in the session ID generation process
  4. Check for weak entropy sources in session ID generation
    Review the session ID generation logic for: time() or time functions, rand() without seeded CSPRNG, stringified hash references, $$ (process ID)
    Affected if Any of these weak entropy sources (epoch time, rand(), hash refs, low-range PID) are used to construct session IDs
  5. Verify session ID predictability
    Generate multiple session IDs and analyze them for patterns: check ID length, check if IDs are incrementing or time-correlated, attempt to predict next ID based on observed IDs
    Affected if Session IDs are predictable, sequential, or time-correlated

You are affected if your application uses Solstice::Session to generate session IDs and the generation relies on MD5 combined with epoch time, rand(), hash references, or process IDs as entropy sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace the session ID generation with a cryptographically secure random number generator (CSPRNG) such as Bytes::Random::Secure or Crypt::PRNG, and generate session IDs with sufficient entropy (minimum 128 bits).

Fix this in Solstice\ Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5085 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-5085 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data