Description
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.
Published: 2026-09-09
Score: 5.3 Medium
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability arises because tirreno fails to regenerate the session identifier after successful authentication, leaving the session ID unchanged. As a result, an attacker who can predefine a session ID for a target—such as via a man‑in‑the‑middle position, cross‑site scripting, or subdomain cookie‑injection—can later exploit that same session to access the victim’s authenticated account. This flaw falls under CWE‑384 and allows an attacker to hijack sessions without requiring any privileged access.

Affected Systems

The affected product is tirrenotechnologies’ tirreno framework, with all releases before version 0.10.0 vulnerable. Updating to tirreno v0.10.0 or newer removes the defect because the session ID is regenerated and the prior session is destroyed upon successful login.

Risk and Exploitability

The CVSS score of 5.3 indicates moderate severity, and the EPSS score is not available, though the vulnerability is not listed in the CISA KEV catalog. Nevertheless, the attack requires the attacker to set a session identifier ahead of authentication, a condition that can arise in realistic scenarios such as compromised network links or unmitigated XSS. Once the session hijack succeeds, the attacker can operate under the victim’s credentials, potentially accessing confidential data or performing privileged actions. Therefore, while the exploitation difficulty is moderate, the impact on confidentiality and integrity can be significant.

Generated by OpenCVE AI on September 9, 2026 at 15:05 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade tirreno to version 0.10.0 or newer, which regenerates the session identifier after successful authentication and destroys the previous session.
  • Configure tirreno’s session cookies to include the HttpOnly, Secure, and SameSite attributes to reduce the risk of cookie theft or replay by third parties.
  • Audit and remediate any cross‑site scripting or subdomain cookie‑injection vulnerabilities that could enable attackers to set a known session identifier before authentication.

Generated by OpenCVE AI on September 9, 2026 at 15:05 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 09 Sep 2026 15:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Wed, 09 Sep 2026 13:45:00 +0000

Type Values Removed Values Added
Description 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.
Title tirreno has Session Fixation in Login Authentication
Weaknesses CWE-384
References
Metrics cvssV4_0

{'score': 5.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-09-09T14:04:23.971Z

Reserved: 2026-07-20T18:31:39.291Z

Link: CVE-2026-64857

cve-icon Vulnrichment

Updated: 2026-09-09T14:04:20.822Z

cve-icon NVD

Status : Received

Published: 2026-09-09T14:17:13.073

Modified: 2026-09-09T15:17:08.107

Link: CVE-2026-64857

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-09T15:15:04Z

Weaknesses