webpy web.py 0.76 is vulnerable to Insufficient Session Expiration. The application's session management relies on periodic cleanup to expire sessions instead of checking the last-access time when a session is loaded. As a result, an expired session whose record has not yet been cleaned up can still be replayed and used, allowing an attacker holding a previously valid session cookie to continue accessing protected resources after the configured idle timeout.
CVE-2026-79313
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-22. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(high)
- EG Risk
- 59(Track)EG Risk 59/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 computedSeverity98% × 45%Exploitation1% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 45%
- KEV
- Not listed
Published
September 22, 2026
Last Modified
September 22, 2026
Advisory Details (2)
Auto-updated Sep 22, 2026GitHub - webpy/webpy: web.py is a web framework for python that is as simple as it is powerful. · GitHub
https://github.com/webpy/webpyTraceLoom/CVEs/CVE-2026-79313.md at main · lichoin/TraceLoom · GitHub
https://github.com/lichoin/TraceLoom/blob/main/CVEs/CVE-2026-79313.mdVendor Advisories for CVE-2026-79313(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 22× in last 7d / 22× 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-24 02:06 UTCGHSA enrichment
- 2026-09-23 21:53 UTCEG score recompute
- 2026-09-23 21:53 UTCGHSA enrichment
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-23 17:39 UTCGHSA enrichment
- 2026-09-23 13:26 UTCGHSA enrichment
- 2026-09-23 09:12 UTCGHSA enrichment
- 2026-09-23 04:59 UTCGHSA enrichment
- 2026-09-23 00:45 UTCEG score recompute
- 2026-09-23 00:45 UTCGHSA enrichment
- 2026-09-22 20:32 UTCEG score recompute▲ 9.80
- 2026-09-22 20:32 UTCGHSA enrichment
- 2026-09-22 20:32 UTCNVD updateCVSS v3 → 9.8 · severity → CRITICAL
- 2026-09-22 20:12 UTCEG score recompute▼ 9.80
- 2026-09-22 20:12 UTCGHSA enrichment
- 2026-09-22 20:11 UTCNVD update
- 2026-09-22 19:23 UTCEG score recompute▲ 9.80
- 2026-09-22 19:23 UTCGHSA enrichment
- 2026-09-22 19:23 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
- 2026-09-22 15:18 UTCNVD update
- 2026-09-22 14:50 UTCEG score recompute
- 2026-09-22 14:50 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-613
Frequently asked(5)
What is CVE-2026-79313?
When was CVE-2026-79313 disclosed?
Is CVE-2026-79313 actively exploited?
What is the CVSS score of CVE-2026-79313?
How do I remediate CVE-2026-79313?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-79313
Is Your Infrastructure Affected by CVE-2026-79313?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.