CVE-2026-34727 | go-vikunja up to 2.2.x OIDC Call improper authentication (GHSA-8jvc-mcx6-r4cg)

VDB-356907 · CVE-2026-34727 · GHSA-8JVC-MCX6-R4CG GO-VIKUNJA UP TO 2.2.X OIDC CALL IMPROPER AUTHENTICATION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 6.4 $0-$5k 0.44+ Summaryinfo A vulnerability was found in go-vikunja vikunja up to 2.2.x. It has been classified as critical. Affected by this issue is some unknown functionality of the component OIDC Call Handler. Performing a manipulation results in improper authentication. This vulnerability is reported as CVE-2026-34727. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is recommended. Detailsinfo A vulnerability, which was classified as critical, was found in go-vikunja vikunja up to 2.2.x. This affects an unknown code block of the component OIDC Call Handler. The manipulation with an unknown input leads to a improper authentication vulnerability. CWE is classifying the issue as CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is: Vikunja is an open-source self-hosted task management platform. Prior to 2.3.0, the OIDC callback handler issues a full JWT token without checking whether the matched user has TOTP two-factor authentication enabled. When a local user with TOTP enrolled is matched via the OIDC email fallback mechanism, the second factor is completely skipped. This vulnerability is fixed in 2.3.0. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-34727 since 03/30/2026. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. Upgrading to version 2.3.0 eliminates this vulnerability. Productinfo Vendor go-vikunja Name vikunja Version 2.0 2.1 2.2 Website Product: https://github.com/go-vikunja/vikunja/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 6.5 VulDB Meta Temp Score: 6.4 VulDB Base Score: 5.6 VulDB Temp Score: 5.4 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 7.4 CNA Vector (GitHub_M): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Improper authentication CWE: CWE-287 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: vikunja 2.3.0 Timelineinfo 03/30/2026 CVE reserved 04/10/2026 +11 days Advisory disclosed 04/10/2026 +0 days VulDB entry created 04/10/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: GHSA-8jvc-mcx6-r4cg Status: Confirmed CVE: CVE-2026-34727 (🔒) GCVE (CVE): GCVE-0-2026-34727 GCVE (VulDB): GCVE-100-356907 Entryinfo Created: 04/10/2026 20:37 Changes: 04/10/2026 20:37 (65) Complete: 🔍 Cache ID: 99:B5D:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸