CVE-2026-129706: In the vulnerability-lookup web application, the Flask-Login session identifier was set to the bare
Source GCVE Database
Not known to be exploited · CVSS 5.3 Medium.
Data as of 16 Nov 2026, 10:35 UTC
Thin evidence
One scorer or none| CNA (CIRCL) | CVSS 4.0 | 5.3 |
|---|
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| vulnerability-lookupvulnerability-lookup | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Mitigation should focus on updating the session management implementation to bind session identifiers to user credentials or session tokens that expire or are invalidated upon password changes or resets. Until a fix is available, administrators should consider invalidating all active sessions upon credential changes and monitoring for suspicious session activity.
Description
The vulnerability-lookup web application uses Flask-Login for session management, where the session identifier is set to the bare numeric user ID. This design flaw causes session identifiers to remain valid indefinitely, even after password changes, account recovery, or administrator resets. An attacker with a valid session can maintain access to the user's account without re-authentication, as the session cookie is not bound to user credentials. This affects the User.get_id() method and the user_loader callback in the application. The vulnerability requires the attacker to already have a valid session and does not depend on special deployment configurations.