CVE-2026-2439
CRITICALDescription
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, * 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. * 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. * UUIDs are identifiers whose mere possession grants access, as per RFC 9562. * The output of the built-in rand() function is predictable and unsuitable for security applications.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 33% of all known CVEs.
References
Related Vulnerabilities
Other CWE-338 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2008-0166 | High | 7.5 | 71% | - | Fix |
| CVE-2009-2367 | Critical | 9.8 | 23% | - | - |
| CVE-2024-29868 | Critical | 9.1 | 6.0% | - | - |
| CVE-2024-31497 | Medium | 5.9 | 5.8% | - | Fix |
| CVE-2021-43799 | High | 8.6 | 5.4% | - | Fix |
| CVE-2008-3280 | Medium | 5.9 | 4.0% | - | - |
Common questions
How do I fix CVE-2026-2439?
Upgrade concierge\ to 0.8.5 or later.
Is CVE-2026-2439 being actively exploited?
Not that we know of. CVE-2026-2439 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.40% is the estimated probability that it will be exploited in the next 30 days. That is higher than 33% of all scored CVEs.
How severe is CVE-2026-2439?
CVE-2026-2439 has a CVSS v3 base score of 9.8, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-2439 affect?
Published advisories record a fix for concierge\ (NVD). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-2439
Markdown
[](https://tridentstack.com/cve/CVE-2026-2439)HTML
<a href="https://tridentstack.com/cve/CVE-2026-2439"><img src="https://tridentstack.com/cve/badge/CVE-2026-2439.svg" alt="CVE-2026-2439"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-03-10.