Vikunja: TOTP secret is readable after enrollment, no step-up auth — GHSA-88F6-4RJV-X774

Summary

### Summary Once a user has TOTP enabled, the API still hands back the raw shared secret to anyone holding that account's access token. Reading it doesn't ask for the password, even though disabling TOTP does. So a stolen token, an XSS, or a browser left open is enough to copy the second factor into your own authenticator and keep generating valid codes indefinitely. ### Details `GET /api/v1/user/settings/totp`…

Timeline

Published by source

2026-10-09

Risk context

• Reported severity or threat level: medium.
• Reported CVSS score: 5.3 out of 10.
• Reported EPSS value: 0.00346.
• Review exposure for the affected product or family: go: code.vikunja.io/api.

Product

go: code.vikunja.io/api

What to do

General, cautious steps (verify details in the official source):

• Review exposure and plan remediation based on risk and environment.
• Identify affected product versions in your inventory and verify whether you are impacted.
• Apply vendor patches/updates or recommended mitigations as soon as available.
• Read the official advisory for exact affected versions and remediation steps.

Official advisory

• Read the official source
• CVE Record
• NVD

Evidence and provenance

Canonical advisory ID

GHSA-88F6-4RJV-X774

Source

GitHub

Vendor

GitHub

Published by source

2026-10-09

Last source activity

2026-10-09

Additional identifiers

CVE-2026-91982

Curated by

hlukh.ch

Related advisories and connections

These advisories are connected by shared CVE, product, vendor, source, or time signals.