mayswind ezBookkeeping before 2.0.0 fails to invalidate TOTP passcodes after use, allowing attackers to replay captured codes within the acceptance window. Attackers with stolen credentials can authenticate and reuse a captured passcode against multiple authorization attempts for approximately 90 seconds without detection.
CVE-2026-94112
Score 6.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-20. a secondary CVSS source baseline 6.8; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.8
- EG Score
- 6.8(high)
- EG Risk
- 31(Track)EG Risk 31/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 computedSeverity68% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 31%
- KEV
- Not listed
Published
September 20, 2026
Last Modified
September 24, 2026
Advisory Details (4)
Auto-updated Sep 20, 2026mayswind ezBookkeeping before 2.0.0 TOTP Replay Attack | Advisories | VulnCheck
https://www.vulncheck.com/advisories/mayswind-ezbookkeeping-before-2.0.0-totp-replay-attackTOTP Replay Attack - Same Code Accepted Twice Within Valid Window (RFC 6238 Violation) · Advisory · mayswind/ezbookkeeping · GitHub
https://github.com/mayswind/ezbookkeeping/security/advisories/GHSA-p6qr-48g6-97q3v2.0.0
Patch available: mayswind/ezbookkeeping v2.0.0
https://github.com/mayswind/ezbookkeeping/releases/tag/v2.0.0commit 3dd6286d7a3a (mayswind/ezbookkeeping)
Fix landed in mayswind/ezbookkeeping commit 3dd6286d7a3a — awaiting tagged release
https://github.com/mayswind/ezbookkeeping/commit/3dd6286d7a3ab0f980a6d36339b9c9c4df9467e4Vendor Advisories for CVE-2026-94112(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 19× in last 7d / 19× 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 21:18 UTCEG score recompute
- 2026-09-24 21:18 UTCGHSA enrichment
- 2026-09-24 14:04 UTCEPSS rescore
- 2026-09-24 02:10 UTCEG score recompute
- 2026-09-24 02:10 UTCGHSA enrichment
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-22 23:47 UTCEG score recompute
- 2026-09-22 23:47 UTCGHSA enrichment
- 2026-09-22 16:01 UTCEPSS rescore
- 2026-09-21 21:23 UTCEG score recompute
- 2026-09-21 21:23 UTCGHSA enrichment
- 2026-09-21 21:09 UTCEPSS rescore
- 2026-09-21 20:48 UTCEG score recompute
- 2026-09-21 20:48 UTCGHSA enrichment
- 2026-09-21 14:49 UTCEG score recompute
- 2026-09-21 14:49 UTCGHSA enrichment
- 2026-09-20 12:22 UTCEG score recompute
- 2026-09-20 12:02 UTCEG score recompute
- 2026-09-20 12:01 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-94112?
When was CVE-2026-94112 disclosed?
Is CVE-2026-94112 actively exploited?
What is the CVSS score of CVE-2026-94112?
How do I remediate CVE-2026-94112?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-94112
Is Your Infrastructure Affected by CVE-2026-94112?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.