CVE-2026-33677

Vikjuna: Webhook BasicAuth Credentials Exposed to Read-Only Project Collaborators via API

• Credential theft: Any user with read-only access to a project can steal BasicAuth credentials configured on that project's webhooks. These credentials may grant access to external services (CI/CD systems, notification endpoints, third-party APIs).
• Lateral movement: Stolen credentials could be reused to authenticate against external systems that the webhook receiver protects.
• Broad exposure surface: Credentials are exposed to all project readers, including users granted access through team shares and link shares (with read+ permission level).

CVE-2026-33677 has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.2.1); upgrading removes the vulnerable code path.

Kodem intelligence

In pkg/models/webhooks.go, add masking for BasicAuth fields alongside the existing Secret masking (around line 237):

for _, webhook := range ws {
	webhook.Secret = ""
	webhook.BasicAuthUser = ""
	webhook.BasicAuthPassword = ""
	if createdBy, has := users[webhook.CreatedByID]; has {
		webhook.CreatedBy = createdBy
	}
}

Apply the same fix in pkg/routes/api/v1/user_webhooks.go (around line 64):

for _, w := range ws {
	w.Secret = ""
	w.BasicAuthUser = ""
	w.BasicAuthPassword = ""
	if createdBy, has := users[w.CreatedByID]; has {
		w.CreatedBy = createdBy
	}
}

1. What is CVE-2026-33677? CVE-2026-33677 is a medium-severity security vulnerability in code.vikunja.io/api (go), affecting versions <= 2.2.0. It is fixed in 2.2.1.
2. How severe is CVE-2026-33677? CVE-2026-33677 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of code.vikunja.io/api are affected by CVE-2026-33677? code.vikunja.io/api (go) versions <= 2.2.0 is affected.
4. Is there a fix for CVE-2026-33677? Yes. CVE-2026-33677 is fixed in 2.2.1. Upgrade to this version or later.
5. Is CVE-2026-33677 exploitable, and should I be worried? Whether CVE-2026-33677 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-33677 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-33677? Upgrade code.vikunja.io/api to 2.2.1 or later.