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

Published Aug 23, 2026
·
Updated

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.

Affected Software

1 affected component
Apache::AppSamurai::Util<=1.01

Event History

Aug 23, 2026
CVE Published
via MITRE·07:18 PM
Data Sourced
via MITRE·07:18 PM
DescriptionWeakness
Data Sourced
via NVD·08:16 PM
DescriptionWeakness

Frequently Asked Questions

1

What information does an attacker need to exploit this issue?

The attacker needs to know the second in which the target session was created and the process ID of the worker that created it. They can then enumerate candidate session keys and try the resulting cookies against the server.

2

Are normal logins affected by default?

Yes. CreateSession invokes CreateSessionAuthKey with an empty key source on every login. The optional Keysource directive is the only route to the alternate branch.

3

Does exploitation require access to the configured server key?

No. The configured server key is used to compute the session ID and encrypt stored session data, but an attacker can test candidate cookies against the server, which performs validation using that key.

4

What could an attacker gain if exploitation succeeds?

An attacker can recover a victim's session cookie and bypass authentication for the protected resources available to that session.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203