Quick answers
- Is CVE-2025-70949 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-70949 being exploited in the wild.
- How severe is CVE-2025-70949?
- Low severity, with a CVSS score of 3.1, published 5 March 2026.
- Which products and versions are affected?
- @perfood/couch-auth (npm) SEMVER:introduced=0,last_affected=0.26.0.
- Is there a fix for CVE-2025-70949?
- 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-2025-70949 attacked?
- It is attacked over the network.
- Am I affected by CVE-2025-70949?
- Check whether you run @perfood/couch-auth (npm) 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.
Technical details
The vulnerability is a timing side-channel attack (CWE-208) in @perfood/couch-auth v0.26.0 that allows attackers to infer sensitive authentication tokens through observable differences in response times. The authentication logic does not use constant-time comparison functions when validating tokens, making it possible for a remote attacker over a network to measure timing variations and progressively guess valid tokens. No user interaction or authentication is required to exploit this vulnerability. An attacker can leverage these timing differences to bypass authentication mechanisms and gain unauthorized access. A patch should implement constant-time token comparison to mitigate this issue.
Affected products
- perfood @perfood/couch-auth 0.26.0 and earlier
Identifiers
- CVE-2025-70949
- GHSA-mjqr-5c55-g77h
Timeline
- 2026-03-05: disclosed
- 2026-03-05: advisory