Quick answers
- Is CVE-2026-74841 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-74841 being exploited in the wild.
- How severe is CVE-2026-74841?
- Informational severity, published 5 November 2026.
- Which products and versions are affected?
- <UNKNOWN>.
- Is there a fix for CVE-2026-74841?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-74841 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-74841?
- Check whether you run <UNKNOWN>. 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.
Technical details
ContextFilter and LoginWorker construct per-tenant delegator names from an unauthenticated userTenantId request parameter and request resolution before tenant validation. DelegatorFactory caches all resolution attempts, including failures, with no eviction policy; an attacker can exploit this by sending many requests with unique invalid tenant IDs to unboundedly grow the cache and exhaust system resources.
Affected products
- <UNKNOWN>
Timeline
- 2026-11-05: disclosed