Authentication bypass via stale session replay
Published Sep 22, 2026 · Updated Sep 22, 2026
Insufficient session expiration in webpy web.py 0.76 allows remote authenticated users to retain access with an expired session cookie. The Session._load path accepts a syntactically valid identifier while _check_expiry tests only whether its record remains in the store; age enforcement occurs only during periodic cleanup. Exploitation requires a previously valid cookie and a stale record between cleanup runs, extending access to application-protected resources.
Summary
What happened
Insufficient session expiration in webpy web.py 0.76 allows remote authenticated users to retain access with an expired session cookie. The Session._load path accepts a syntactically valid identifier while _check_expiry tests only whether its record remains in the store; age enforcement occurs only during periodic cleanup. Exploitation requires a previously valid cookie and a stale record between cleanup runs, extending access to application-protected resources.
The record
- CVE
- CVE-2026-79313
- Published
- Sep 22, 2026
- Updated
- Sep 22, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1550.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 22, 2026CVE publishedPublication date reported by the CVE source.
- Sep 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started