Skip to main content
No exploitation reportedFix available

CVE-2026-5080

No exploitation reported by the sources we read.

  • Published2026-04-30
  • WeaknessCWE-338 · CWE-340

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

Dancer::Session::Abstract versions through 1.3522 for Perl generates session ids insecurely. The session id is generated from summing the character codepoints of the absolute pathname with the process id, the epoch time and calls to the built-in rand() function to return a number between 0 and 999-billion, and concatenating that result three times. The path name might be known or guessed by an attacker, especially for applications known to be written using Dancer with standard installation locations. The epoch time can be guessed by an attacker, and may be leaked in the HTTP header. The process id comes from a small set of numbers, and workers may have sequential process ids. The built-in rand() function is seeded with 32-bits and is considered unsuitable for security applications. Predictable session ids could allow an attacker to gain access to systems.

Timeline

dates in UTC
  1. 2026-04-3012:16CVE publishedNVD

Versions per branch

NVD
Perldancer dancer\
BranchAffectedFixed in
—= \no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As CPANSec, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • BIGPRESH Dancer::Session::Abstractother versions: not affected

    package Dancerhttps://cpan.org/modules

    Affected
    • ≤ 1.3522no fix statedcustom

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-04-30

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • libdancer-perlUbuntu:26.10all versions · no fixed version listed
  • libdancer-perlUbuntu:26.04:LTSall versions · no fixed version listed
  • libdancer-perlUbuntu:25.10all versions · no fixed version listed
  • libdancer-perlUbuntu:24.04:LTSall versions · no fixed version listed
  • libdancer-perlUbuntu:22.04:LTSall versions · no fixed version listed
  • libdancer-perlUbuntu:20.04:LTSall versions · no fixed version listed
  • libdancer-perlUbuntu:18.04:LTSall versions · no fixed version listed
  • libdancer-perlUbuntu:16.04:LTSall versions · no fixed version listed

3 more package ranges on OSV.dev

Full record on NVD

Fix

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Published
2026-04-30
Last Modified
2026-10-26
NVD status
Analyzed
GitHub Advisory
GHSA-97p2-62hq-g269

Frequently asked questions

What is CVE-2026-5080?

Dancer::Session::Abstract versions through 1.3522 for Perl generates session ids insecurely. The session id is generated from summing the character codepoints of the absolute pathname with the process id, the epoch time and calls to the built-in rand() function to return a number between 0 and 999-billion, and concatenating that result three times. The path name might be known or guessed by an attacker, especially for applications known to be written using Dancer with standard installation locations. The epoch time can be guessed by an attacker, and may be leaked in the HTTP header. The process id comes from a small set of numbers, and workers may have sequential process ids. The built-in rand() function is seeded with 32-bits and is considered unsuitable for security applications. Predictable session ids could allow an attacker to gain access to systems.

Is CVE-2026-5080 actively exploited?

Active exploitation of CVE-2026-5080 has not been confirmed. Its EPSS score was 0.4% on 2026-11-16, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-5080?

CVE-2026-5080 has a CVSS v3 base score of 5.9 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H.

Running libdancer-perl? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record