Cyber Resilience

CVE-2025-70949

Published
05 March 2026
Modified
27 April 2026
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0038 31th percentile
Risk Priority 57 floored blend · peak EPSS

Summary

CVE-2025-70949 is a high-severity Observable Timing Discrepancy (CWE-208) vulnerability in Npmjs (inferred from references). Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Password Guessing (T1110.001); ranked at the 31th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-70949 is an observable timing discrepancy vulnerability, classified under CWE-208 (Observable Timing Discrepancy), affecting the @perfood/couch-auth npm package at version 0.26.0. This flaw enables attackers to access sensitive information through a timing side-channel attack. The vulnerability received a CVSS v3.1 base score of 7.5, reflecting high confidentiality impact with network accessibility, low attack complexity, no required privileges or user interaction, and unchanged scope.

Remote attackers can exploit this vulnerability over the network without authentication or user involvement. By measuring response time differences in the authentication process, attackers can infer sensitive data, such as credentials or other protected information, potentially leading to unauthorized disclosure.

Mitigation guidance and further details are available in advisories linked to the CVE, including a GitHub Gist at https://gist.github.com/0xHunterr/38aab644874ca9f4646524c5b01cfe5e, the package repository at https://github.com/perfood/couch-auth, and the npm page at https://www.npmjs.com/package/@perfood/couch-auth. Security practitioners should review these resources for patching instructions or workarounds specific to the affected version.

EU & UK References

Vulnerability Data

An observable timing discrepancy in @perfood/couch-auth v0.26.0 allows attackers to access sensitive information via a timing side-channel.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1110.001 Password Guessing Credential Access
Adversaries with no prior knowledge of legitimate credentials within the system or environment may guess passwords to attempt access to accounts.
T1087 Account Discovery Discovery
Adversaries may attempt to get a listing of valid accounts, usernames, or email addresses on a system or within a compromised environment.
T1087.001 Local Account Discovery
Adversaries may attempt to get a listing of local system accounts.
T1087.002 Domain Account Discovery
Adversaries may attempt to get a listing of domain accounts.
T1087.003 Email Account Discovery
Adversaries may attempt to get a listing of email addresses and accounts.
T1087.004 Cloud Account Discovery
Adversaries may attempt to get a listing of cloud accounts.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-23892Shared CWE-208
CVE-2026-40263Shared CWE-208
CVE-2026-43606Shared CWE-208
CVE-2024-41828Shared CWE-208
CVE-2026-40972Shared CWE-208
CVE-2026-5086Shared CWE-208
CVE-2026-13758Shared CWE-208
CVE-2024-52307Shared CWE-208
CVE-2025-59350Shared CWE-208
CVE-2025-43754Shared CWE-208

Affected Assets

Npmjs
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V11.2.4

Mitigating Controls (NIST 800-53 r5) AI

Developer testing can include timing analysis or side-channel test cases that reveal observable timing discrepancies.

Engineering principles can mandate constant-time algorithms and side-channel resistance so timing discrepancies are never introduced.

Requiring approved cryptographic modules and algorithms implicitly demands implementations free of observable timing leaks.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require constant-time implementations that eliminate observable timing discrepancies.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

none

Consistent reference clocks limit the attacker's ability to measure or manipulate timing differences that could reveal internal state or processing paths.

References