Question2Answer through 1.8.8 contains a session invalidation vulnerability that allows attackers with a previously obtained remember-me cookie to retain authenticated access by exploiting the forgot-password reset flow's failure to clear the sessioncode field in qa-include/app/users-edit.php. While the normal password-change flow in qa-include/pages/account.php explicitly clears the sessioncode to invalidate persistent qa_session cookies, the forgot-password handler qa_finish_reset_user() omits this step, allowing any valid persistent cookie issued before the reset to continue authenticating the account after the password reset completes.
CVE-2026-64829
Score 7.4 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-22. the CNA's CVSS baseline 7.4; 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
- 7.4
- EG Score
- 7.4(high)
- EG Risk
- 33(Track)EG Risk 33/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 computedSeverity74% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 19%
- KEV
- Not listed
Published
July 22, 2026
Last Modified
July 28, 2026
Advisory Details (2)
Auto-updated Jul 22, 2026Question2Answer 1.8.8 Session Fixation via Forgot-Password Flow | Advisories | VulnCheck
https://www.vulncheck.com/advisories/question2answer-session-fixation-via-forgot-password-flowInvalidate remember-me sessions after password reset
Upstream fix in progress (PR #1017 · q2a/question2answer, state=open)
https://github.com/q2a/question2answer/pull/1017Vendor Advisories for CVE-2026-64829(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 21× in last 7d / 21× 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-07-28 01:30 UTCGHSA enrichment
- 2026-07-27 19:08 UTCEG score recompute
- 2026-07-27 19:08 UTCGHSA enrichment
- 2026-07-27 14:14 UTCEPSS rescore
- 2026-07-27 05:44 UTCGHSA enrichment
- 2026-07-26 16:34 UTCEG score recompute
- 2026-07-26 16:34 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 03:23 UTCEG score recompute
- 2026-07-26 03:23 UTCGHSA enrichment
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:22 UTCEG score recompute
- 2026-07-22 20:57 UTCEG score recompute
- 2026-07-22 20:03 UTCEG score recompute
- 2026-07-22 20:00 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-64829?
When was CVE-2026-64829 disclosed?
Is CVE-2026-64829 actively exploited?
What is the CVSS score of CVE-2026-64829?
How do I remediate CVE-2026-64829?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-64829
Is Your Infrastructure Affected by CVE-2026-64829?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.