Quick answers
- Is CVE-2026-118986 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118986 being exploited in the wild.
- How severe is CVE-2026-118986?
- Informational severity, published 30 October 2026.
- Which products and versions are affected?
- OETIKER CallBackery before 0.62.0.
- Is there a fix for CVE-2026-118986?
- Yes: fixed in 0.62.0. Until then: Existing weak secrets are invalidated and replaced on startup with secure random bytes, which logs out all users once. Administrators should ensure any leftover insecure .secret files are regenerated before redeploying. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-118986 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-118986?
- Check whether you run OETIKER CallBackery 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: 0.62.0
Existing weak secrets are invalidated and replaced on startup with secure random bytes, which logs out all users once. Administrators should ensure any leftover insecure .secret files are regenerated before redeploying.
Technical details
The vulnerability exists in the session cookie signing mechanism, which derives its secret from two calls to Perl's rand() function seeded with only 32 bits of entropy, resulting in approximately 2^32 possible secrets. An attacker who obtains one signed session cookie can perform an offline brute-force attack to recover the secret and then sign cookies for any user. The fix in version 0.62.0 replaces the weak generator with 32 random bytes and invalidates existing secrets by logging out all users on startup.
Affected products
- OETIKER CallBackery before 0.62.0
Timeline
- 2026-10-30: disclosed
- 2026-10-29: patched