How many CVEs have patched GetAPITokenByID?

1 published CVEs changed GetAPITokenByID in go-vikunja/vikunja, in 1 distinct patches totalling 84 changed lines, between 2026 and 2026.

What is the latest CVE that changed GetAPITokenByID?

CVE-2026-68581 (Vikunja 0.22.0 through 2.3.0 Authentication Bypass via Principal ID Collision), published 2026-08-02, changed lines 58 to 141 of pkg/models/api_tokens.go.

How does GetAPITokenByID compare to the rest of go-vikunja/vikunja?

go-vikunja/vikunja has 37 CVEs with a located fix in total; 1 of them changed GetAPITokenByID.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

go-vikunja/vikunja

Function

GetAPITokenByID

Name: GetAPITokenByID in go-vikunja/vikunja: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

pkg/models/api_tokens.go

Last patched August 2, 2026

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

84

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

GetAPITokenByID in go-vikunja/vikunja was changed by 1 published CVE fixes in 2026, in 1 distinct patches that added or removed 84 lines in total.

go-vikunja/vikunja has 37 CVEs with a located fix in total, so 3% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed GetAPITokenByID, newest first, with the lines each fix touched.

Vikunja 0.22.0 through 2.3.0 Authentication Bypass via Principal ID Collision
CVE-2026-68581 · lines 58–141 · +84 −0
High · CVSS 8.6
EPSS 0.5%2026-08-02

Get an alert when the next CVE fix lands in go-vikunja/vikunja, with the patched functions.

Monitor vikunja CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in go-vikunja/vikunja changed by the most CVE fixes.

convertTodoistToVikunja6 CVEs · pkg/modules/migration/todoist/todoist.go createProjectWithEverything6 CVEs · pkg/modules/migration/create_from_structure.go CanUpdate6 CVEs · pkg/models/project_permissions.go UpdateProject6 CVEs · pkg/models/project.go HashSessionToken6 CVEs · pkg/models/sessions.go RequestDeletion6 CVEs · pkg/user/delete.go

All patched functions in go-vikunja/vikunja

Frequently asked questions

Common questions about CVE fixes to GetAPITokenByID.

How many CVEs have patched GetAPITokenByID?: 1 published CVEs changed GetAPITokenByID in go-vikunja/vikunja, in 1 distinct patches totalling 84 changed lines, between 2026 and 2026.
What is the latest CVE that changed GetAPITokenByID?: CVE-2026-68581 (Vikunja 0.22.0 through 2.3.0 Authentication Bypass via Principal ID Collision), published 2026-08-02, changed lines 58 to 141 of pkg/models/api_tokens.go.
How does GetAPITokenByID compare to the rest of go-vikunja/vikunja?: go-vikunja/vikunja has 37 CVEs with a located fix in total; 1 of them changed GetAPITokenByID.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track go-vikunja/vikunja CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing