# CVE-2025-70949: @perfood/couch-auth has an Observable Timing Discrepancy

> Attackers can exploit timing discrepancies in the authentication library to access sensitive information via a side-channel attack.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Mar 2026
- **Updated:** 6 Mar 2026
- **Also known as:** GHSA-mjqr-5c55-g77h

## What is CVE-2025-70949?

CVE-2025-70949 is a high-severity vulnerability in n/a, published on 5 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-208 (Observable Timing Discrepancy)

## Which versions are affected by CVE-2025-70949?

2 open source packages ship an affected version, including @perfood/couch-auth.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@perfood/couch-auth` | npm | All versions to 0.26.0 | None |
| `@perfood/couch-auth` | npm | All versions to 0.26.0 | None |

## How do I fix CVE-2025-70949?

No fix has been published for CVE-2025-70949 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-70949 being exploited?

There is no known exploitation of CVE-2025-70949 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-70949 and fix it if it is affected.

What it is: CVE-2025-70949 is a high-severity vulnerability in n/a, published on 5 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-70949 in the wild and no public exploit code.

Affected packages and fixed versions:
- @perfood/couch-auth (npm): affected all versions up to 0.26.0; no fix listed
- @perfood/couch-auth (npm): affected all versions up to 0.26.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-70949/ (Markdown: https://insights.sbomify.com/CVE-2025-70949/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-70949
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-70949
- OSV: https://osv.dev/vulnerability/CVE-2025-70949

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-70949/
Summaries are generated and may contain mistakes; the official description above is the record.