CVE-2026-123504: Infoleak

Published Nov 8, 2026
·
Updated

Vikunja from 0.22.0 before 2.7.1 contains an information disclosure vulnerability that allows read-only project members to view full webhook target URLs by listing project webhooks. Attackers can extract incoming-webhook tokens or API keys embedded in targeturl values to post to receiving channels or reuse keys until rotated.

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Vikunja to a version that resolves this vulnerability.

    Fixed in 2.7.1

Event History

Nov 8, 2026
CVE Published
via NVD·02:16 AM
Data Sourced
via NVD·02:16 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

A read-only member of a Vikunja project can exploit it if that project has webhooks configured. The member can list the project webhooks and view the full target URLs.

2

What secrets may be exposed?

Incoming-webhook tokens and API keys embedded in webhook target_url values may be disclosed. An attacker could use those values to post to receiving channels or reuse the keys until they are rotated.

3

What should be done if exposure is suspected?

Rotate any incoming-webhook tokens or API keys embedded in affected webhook target URLs. This limits reuse of credentials that may already have been viewed by read-only project members.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203