p PatchFirst

CVE-2026-19953

CVE-2026-19953 · URI versions before 5.36 for Perl encode non-NFC host names to non-standard punycode labels via missing normalization in nameprep

CVSS 6.5 · Medium · EPSS 0.2% · Fix available

Compare with your installed version

Affected products and known fixed versions are public information. Compare them with your installed version.

Check the installed version:

dpkg-query -W -f='${source:Package} ${binary:Package} ${Version}\n' | awk '$1=="liburi-perl"'

Assess your server’s risks

The free check gives you a rating and a risk summary by technology stack, without signing up. It does not answer whether this particular vulnerability affects you.

Monitoring matches public information against your servers’ software. Detailed findings for your servers include the order of updates.

curl -fsSL https://patchfirst.dev/check.sh | sh
Check your server for free →

Channels carry general technology news; monitoring reports new findings on your servers in your dashboard, through browser notifications, in Telegram or via a webhook.

This page contains facts from public vulnerability sources. Check the original advisory before updating.

URI versions before 5.36 for Perl encode non-NFC host names to non-standard punycode labels via missing normalization in nameprep.

nameprep lowercases each host label but performs no Unicode normalization. IDNA requires a label to be normalized to Form C before it is encoded (RFC 5891), so a label that is not already in NFC is encoded to a different A-label than its normalized form. A label built from the precomposed Devanagari sequence U+0958 U+093E encodes to xn--72b5c without normalization but to xn--11b2fg after NFC normalization, and xn--72b5c does not round-trip back to the original label.

Any caller that reads host() from a URI built from untrusted input and uses it for a security decision (an allow or deny list, an SSRF filter, deduplication, a cache key) sees the non-standard label, while a client that fetches the same URL resolves the NFC form, so the check and the fetch can disagree about the host.

Published
Updated

Fixes in distributions

Stack: system

Affected products and versions

  • liburi-perl Debian 12

    Versions
    • 5.17-1
    • 5.19-1
    • 5.19-2
    • 5.21-1
    • 5.25-1
    • 5.26-1
    All versions (15)
    • 5.27-1
    • 5.28-1
    • 5.29-1
    • 5.30-1
    • 5.34-1
    • 5.34-2
    • 5.35-1
    • 5.36-1
    • 5.37-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • liburi-perl Debian 13

    Versions
    • 5.30-1
    • 5.34-1
    • 5.34-2
    • 5.35-1
    • 5.36-1
    • 5.37-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • liburi-perl Debian 14

    Versions
    • 5.30-1
    • 5.34-1
    • 5.34-2
    • 5.35-1
    Affected ranges
    • ECOSYSTEM: < 5.36-1

    Update to 5.36-1

  • liburi-perl Ubuntu 14.04 LTS

    Versions
    • 1.60-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • liburi-perl Ubuntu 16.04 LTS

    Versions
    • 1.69-1
    • 1.71-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • liburi-perl Ubuntu 18.04 LTS

    Versions
    • 1.72-1
    • 1.72-2
    • 1.73-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • liburi-perl Ubuntu 20.04 LTS

    Versions
    • 1.76-1
    • 1.76-2
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • liburi-perl Ubuntu 22.04 LTS

    Versions
    • 5.08-1
    • 5.10-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • liburi-perl Ubuntu 24.04 LTS

    Versions
    • 5.19-2
    • 5.21-1
    • 5.25-1
    • 5.27-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • liburi-perl Ubuntu 26.10

    Versions
    • 5.34-2build1
    • 5.35-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • liburi-perl Ubuntu 26.04 LTS

    Versions
    • 5.30-1
    • 5.34-2build1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

Original sources

Check your server →