Skip to content
This page tracks the Ubuntu fix status. The vulnerability itself is described on the main CVE page. View CVE-2026-5080 →
Unrated

Vulnerability in libdancer-perl

UBUNTU-CVE-2026-5080 First seen on SecPulse

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as UBUNTU-CVE-2026-5080 has been found in libdancer-perl.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "libdancer-perl UBUNTU-CVE-2026-5080" on the vendor's site.

UBUNTU-CVE-2026-5080 (libdancer-perl)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

What is the problem

A vulnerability (unclassified) exists in libdancer-perl.

Affected scope

Check the vendor advisory for the affected versions of libdancer-perl.

Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

How to fix

Update to the patched release per vendor advisory.

Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'libdancer-perl' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposureidentify
    grep -r 'libdancer-perl' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で libdancer-perl を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Post-deployment verificationverify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

PackageAffected → Fixed
Ubuntu:16.04:LTSlibdancer-perl
All versions→ Not listed
Ubuntu:18.04:LTSlibdancer-perl
All versions→ Not listed
Ubuntu:20.04:LTSlibdancer-perl
All versions→ Not listed
Ubuntu:22.04:LTSlibdancer-perl
All versions→ Not listed
Ubuntu:24.04:LTSlibdancer-perl
All versions→ Not listed
Ubuntu:25.10libdancer-perl
All versions→ Not listed
Ubuntu:26.04libdancer-perl
All versions→ Not listed
Ubuntu:26.04:LTSlibdancer-perl
All versions→ Not listed
Ubuntu:26.10libdancer-perl
All versions→ Not listed

This record does not list fixed versions. Check the article or the vendor advisory in the references for whether and where it is fixed.

Original description The description as published by the source.

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.

Source: OSV.dev (Open Source Vulnerabilities) OSV

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details