Quick answers
- Is CVE-2026-123523 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-123523 being exploited in the wild.
- How severe is CVE-2026-123523?
- Medium severity, with a CVSS score of 6.5, published 8 November 2026.
- Which products and versions are affected?
- Vikunja before 2.7.1.
- Is there a fix for CVE-2026-123523?
- Yes: fixed in 2.7.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-123523 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-123523?
- Check whether you run Vikunja at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2.7.1
Technical details
The avatar endpoint caches resized copies of avatars for each requested size (1–1024) with no TTL or eviction policy, storing them in an unbounded in-memory map. An authenticated attacker uploads a noisy avatar and requests it at many distinct sizes, accumulating roughly 1 GB of memory per account that persists until restart or avatar change. The vulnerability requires authentication but no user interaction from victims, and rate limiting is disabled by default.
Affected products
- Vikunja Vikunja before 2.7.1
Timeline
- 2026-10-22: disclosed
- 2026-11-08: advisory