Skip to main content
VulnerabilityPublished Updated

CVE-2025-70948: couch-auth · A Host Header Injection

Affects couch-authSource CVE Database V5

0

Not known to be exploited · CVSS 9.3 Critical.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
npm@perfood/couch-authpkg:npm/@perfood/couch-authOther threatsAffected
  • =0.26.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-70948, organizations should immediately implement strict validation and sanitization of the HTTP Host header within their applications, ensuring that only expected and authorized hostnames are accepted. Employing a whitelist approach for allowed Host headers can prevent malicious spoofing. Additionally, developers should avoid relying solely on the Host header for security-sensitive operations like token generation or email link construction. Implementing additional verification steps, such as binding reset tokens to user-specific data or using cryptographically signed tokens, can reduce the risk of token interception. Monitoring and logging suspicious HTTP requests with unusual Host headers can help detect exploitation attempts. Until an official patch is released, consider isolating or disabling the vulnerable mailer component if feasible. Organizations should also keep their dependencies up to date and subscribe to security advisories for @perfood/couch-auth to apply patches promptly once available. Conducting security reviews and penetration testing focused on header injection vulnerabilities is recommended to identify similar issues.

Description

A host header injection vulnerability in the mailer component of @perfood/couch-auth v0.26.0 allows attackers to obtain reset tokens and execute an account takeover via spoofing the HTTP Host header.

References

Community reviews

Loading reviews…