tirreno, a security framework, has a session fixation issue in versions prior to 0.10.0. During authentication, tirreno validates the user's credentials and establishes the authenticated session, but it does not call session_regenerate_id() afterward. As a result, the session identifier is not rotated on login, it stays the same before and after authentication. An attacker able to fix a known session identifier in a victim's browser (for example through a network man-in-the-middle position, or a separate cross-site scripting or subdomain cookie-injection issue) could then gain access to the victim's authenticated session. The issue is fixed in v0.10.0. The session identifier is now regenerated on successful authentication, and the previous session is destroyed. There is no configuration-level workaround.
CVE-2026-64857
This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% 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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EG Risk
- 24(Track)EG Risk 24/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 computedSeverity53% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 19%
- KEV
- Not listed
Published
September 9, 2026
Last Modified
September 9, 2026
Advisory Details (2)
Auto-updated Sep 9, 2026v0.10.0
Patch available: tirrenotechnologies/tirreno v0.10.0
https://github.com/tirrenotechnologies/tirreno/releases/tag/v0.10.0CWE-384: Session Fixation in Login Authentication · Advisory · tirrenotechnologies/tirreno · GitHub
Affected: v0.10.0. The session identifier is now regenerated on successful
https://github.com/tirrenotechnologies/tirreno/security/advisories/GHSA-gwcm-4p9m-9mvrWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 16× 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.
- 2026-09-19 06:31 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 05:29 UTCEG score recompute
- 2026-09-17 04:26 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-16 03:23 UTCEG score recompute
- 2026-09-14 01:16 UTCEG score recompute
- 2026-09-13 00:14 UTCEG score recompute
- 2026-09-11 23:12 UTCEG score recompute
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 09:37 UTCEPSS rescore
- 2026-09-09 15:28 UTCEG score recompute
- 2026-09-09 14:20 UTCEG score recompute
- 2026-09-09 13:45 UTCEG score recompute
- 2026-09-09 13:44 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-64857?
When was CVE-2026-64857 disclosed?
Is CVE-2026-64857 actively exploited?
What is the CVSS score of CVE-2026-64857?
How do I remediate CVE-2026-64857?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-64857
Is Your Infrastructure Affected by CVE-2026-64857?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.