CVE-2026-91982

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreHIGH confidence

Score 4.3 from GitHub Security Advisory published 2026-09-15. a secondary CVSS source baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this weekElevated
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Vikunja before 2.6.0 continues to expose the raw TOTP shared secret after enrollment through the GET /api/v1/user/settings/totp and /api/v1/user/settings/totp/qrcode endpoints without re-authentication. Attackers with a valid access token can read the secret, import it into their own authenticator, and generate valid codes indefinitely to defeat the second factor and enable account takeover.

CVSS v3
4.3
EG Score
4.3(high)
EG Risk
35(Track)
EG Risk 35/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 computed
Severity43% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

September 15, 2026

Last Modified

September 17, 2026

Advisory Details (2)

Auto-updated Sep 15, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

Vikunja before 2.6.0 TOTP Secret Disclosure via API | Advisories | VulnCheck

https://www.vulncheck.com/advisories/vikunja-before-2.6.0-totp-secret-disclosure-via-api
github Patch Available🟡 PoC Available

TOTP secret is readable after enrollment, no step-up auth · Advisory · go-vikunja/vikunja · GitHub

https://github.com/go-vikunja/vikunja/security/advisories/GHSA-88f6-4rjv-x774

Vendor Advisories for CVE-2026-91982(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.

  1. 2026-09-20 20:16 UTCEPSS rescore
  2. 2026-09-20 17:35 UTCGHSA enrichment
  3. 2026-09-19 17:43 UTCEG score recompute
  4. 2026-09-19 17:43 UTCGHSA enrichment
  5. 2026-09-18 19:28 UTCEPSS rescore
  6. 2026-09-18 17:56 UTCEG score recompute
  7. 2026-09-18 17:56 UTCGHSA enrichment
  8. 2026-09-17 19:32 UTCEPSS rescore
  9. 2026-09-17 18:08 UTCEG score recompute
  10. 2026-09-17 18:08 UTCGHSA enrichment
  11. 2026-09-17 15:29 UTCEG score recompute
  12. 2026-09-17 15:29 UTCGHSA enrichment
  13. 2026-09-16 21:07 UTCGHSA enrichment
  14. 2026-09-16 17:55 UTCEG score recompute
  15. 2026-09-16 17:55 UTCGHSA enrichment
  16. 2026-09-16 14:09 UTCEPSS rescore
  17. 2026-09-15 16:32 UTCEG score recompute
  18. 2026-09-15 15:23 UTCEG score recompute
  19. 2026-09-15 15:22 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-91982?
CVE-2026-91982 is a medium vulnerability published on September 15, 2026. Vikunja before 2.6.0 continues to expose the raw TOTP shared secret after enrollment through the GET /api/v1/user/settings/totp and /api/v1/user/settings/totp/qrcode endpoints without re-authentication. Attackers with a valid access token can read the secret, import it into their own authenticator,…
When was CVE-2026-91982 disclosed?
CVE-2026-91982 was first published in the National Vulnerability Database on September 15, 2026, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-91982 actively exploited?
CVE-2026-91982 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 79.7% of all scored CVEs.
What is the CVSS score of CVE-2026-91982?
CVE-2026-91982 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-91982?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-91982, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-91982

Explore →

Is Your Infrastructure Affected by CVE-2026-91982?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs