Quick answers
- Is CVE-2026-118505 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118505 being exploited in the wild.
- How severe is CVE-2026-118505?
- Informational severity, published 3 November 2026.
- Which products and versions are affected?
- Team-Alembic Ash Authentication 5.0.0-rc.4 to before 5.0.0-rc.16.
- Is there a fix for CVE-2026-118505?
- Yes: fixed in 5.0.0-rc.16. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-118505 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-118505?
- Check whether you run Team-Alembic Ash Authentication 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: 5.0.0-rc.16
Technical details
The brute_force_strategy preparation is only applied to generated actions, not to custom resource-defined actions. When developers override password, magic link, or OTP sign-in actions, the preparation is skipped; additionally, OTP sign-in with registration enabled is a create action, which do not execute preparations. An unauthenticated attacker can make unlimited authentication attempts without rate limiting.
Affected products
- team-alembic ash_authentication 5.0.0-rc.4 to before 5.0.0-rc.16
Timeline
- 2026-11-03: disclosed