Threadlinqs IntelligenceStart free

Weakness · BaseCWE-613

CWE-613: Insufficient Session Expiration

Base

As of 2026-11-19, CWE-613 (Insufficient Session Expiration) underlies 22 CVEs tracked by Threadlinqs, none of them in the CISA Known Exploited Vulnerabilities catalog, and is cited by 20 tracked threats.

CVEs
22Mapped to CWE-613
CISA KEV
0None listed yet
Critical
1CVSS v3 critical CVEs
Threats
20Tracked campaigns citing it
Likelihood
—MITRE likelihood of exploit

Last updated:

What is CWE-613?

According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization."

CWE-613 is a base-level weakness in MITRE’s Common Weakness Enumeration. Applicable platforms: Language: Not Language-Specific; Technology: Web Based; Technology: Web Server.

Source: MITRE CWE (CWE-613 definition, reproduced verbatim). Counts and linkage below are Threadlinqs data.

Consequences

  • Access Control — Bypass Protection Mechanism

Source: MITRE CWE, common consequences.

How CWE-613 is exploited in the wild

Threadlinqs maps 22 CVEs to CWE-613, published between 2023-07-11 and 2026-11-15. None of them is in the CISA KEV catalog yet. By CVSS v3 severity the set splits into 1 critical, 2 high, 11 medium, 2 low. The highest EPSS score in the set is 1.1% (CVE-2024-50562), the modelled probability of exploitation in the next 30 days. 20 tracked threats reference CWE-613 directly or through a CVE it covers; the most recent is “44-Hour Machine-Speed Cloud Intrusion at Barracuda via Leaked Vendor Access Key, Linked to ARTEX AI Pentest Framework” (2026-11-17). Affected products concentrate in Fortinet (4), Apache Software Foundation (2), IBM (2), among 17 vendors in total.

Vulnerabilities (CVEs)

All 22 CVEs mapped to CWE-613, CISA KEV first, then by CVSS score.

Affected vendors

Threat activity

20 tracked threats cite CWE-613:

Mitigations

  • Implementation: Set sessions/credentials expiration date.

Source: MITRE CWE, potential mitigations.

Detection methods (MITRE CWE)

  • Automated Static Analysis (effectiveness: High): Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)

Source: MITRE CWE, detection methods. Threadlinqs detection rules for the threats above are Blue tier and higher.