---
id: CVE-2026-19565
title: >-
  Apache::AppSamurai::Util versions through 1.01 for Perl generate predictable
  session authentication keys from the clock and process id in
  CreateSessionAuthKey.


  CreateSessionAuthKey runs five rounds of SHA-256, each over a fresh Time::Hi…
summary: >-
  Apache::AppSamurai::Util versions through 1.01 for Perl generate predictable
  session authentication keys from the clock and process id in
  CreateSessionAuthKey.


  CreateSessionAuthKey runs five rounds of SHA-256, each over a fresh Time::Hi…
severity: low
cvss: 3.7
cvssVector: 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N'
cwe:
  - CWE-341
published: '2026-08-23'
updated: '2026-10-14'
sourceUpdated: '2026-10-14T13:10:00.187'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-19565'
references:
  - url: >-
      https://metacpan.org/release/PAULDOOM/Apache-AppSamurai-1.01/source/lib/Apache/AppSamurai.pm#L1446-1533
    label: 9b29abf9-4ab0-4765-b253-1875cd9b441e
  - url: >-
      https://metacpan.org/release/PAULDOOM/Apache-AppSamurai-1.01/source/lib/Apache/AppSamurai/Util.pm#L106-135
    label: 9b29abf9-4ab0-4765-b253-1875cd9b441e
  - url: 'http://www.openwall.com/lists/oss-security/2026/08/23/4'
    label: af854a3a-2127-422b-91ae-364da2661108
tags:
  - nvd
epss: 0.00411
epssPercentile: 0.33549
ingestedAt: '2026-10-14T13:30:58.552Z'
---

## Overview

Apache::AppSamurai::Util versions through 1.01 for Perl generate predictable session authentication keys from the clock and process id in CreateSessionAuthKey.

CreateSessionAuthKey runs five rounds of SHA-256, each over a fresh Time::HiRes reading formatted to six decimal places, the running digest, and the process id. CreateSession calls it with an empty key source on every login, and the optional Keysource directive is the only route to the other branch. The result is 64 hex characters. The microsecond field of the first reading takes one of a million values, the later readings follow it within microseconds, and the process id is drawn from a small range.

The key is returned to the browser as the session cookie, and is combined with the configured server key to compute the session id and to encrypt the stored session data. An attacker who knows the second in which a session was created and the process id of the worker that created it can enumerate candidate keys and recover the victim's cookie, bypassing authentication for the protected resources. Each candidate has to be tried against the server, which validates the cookie with a key the attacker does not hold.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.