CVE-2026-19565

LOWPre-NVD 3.73.7
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 3.7 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cisa-adp, epss
Trending — 5 sources updated this week
3.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
3.7
EG Score
3.7(medium)
EG Risk
17(Track)
EG Risk 17/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity37% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

August 23, 2026

Last Modified

August 25, 2026

Vendor Advisories for CVE-2026-19565(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 12× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-25 20:35 UTCGHSA enrichment
  2. 2026-08-25 19:35 UTCEG score recompute 3.70
  3. 2026-08-25 19:35 UTCGHSA enrichment
  4. 2026-08-25 19:34 UTCMITRE cvelistV5CVSS v3 → 3.7 · severity → LOW
  5. 2026-08-25 13:48 UTCEPSS rescore
  6. 2026-08-23 22:30 UTCGHSA enrichment
  7. 2026-08-23 22:29 UTCNVD update
  8. 2026-08-23 22:11 UTCGHSA enrichment
  9. 2026-08-23 22:10 UTCMITRE cvelistV5
  10. 2026-08-23 20:24 UTCNVD update
  11. 2026-08-23 19:31 UTCEG score recompute
  12. 2026-08-23 19:30 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-19565?
CVE-2026-19565 is a low vulnerability published on August 23, 2026. 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…
When was CVE-2026-19565 disclosed?
CVE-2026-19565 was first published in the National Vulnerability Database on August 23, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-19565 actively exploited?
CVE-2026-19565 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 79.8% of all scored CVEs.
What is the CVSS score of CVE-2026-19565?
CVE-2026-19565 has a CVSS v3.1 base score of 3.7 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-19565?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-19565, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-19565

Explore →

Is Your Infrastructure Affected by CVE-2026-19565?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.