Session hijacking via uncleared authentication objects
Published Nov 20, 2025 · Updated Nov 20, 2025
Sensitive-data exposure in perfood CouchAuth 0.21.2 and earlier allows attackers to read session credentials from process memory. The session-creation path in src/user.ts copies token and password values into JavaScript objects without explicitly clearing them after use. Memory-dump, debugger, or equivalent process-memory access is required; recovered credentials enable session hijacking.
Summary
What happened
Sensitive-data exposure in perfood CouchAuth 0.21.2 and earlier allows attackers to read session credentials from process memory. The session-creation path in src/user.ts copies token and password values into JavaScript objects without explicitly clearing them after use. Memory-dump, debugger, or equivalent process-memory access is required; recovered credentials enable session hijacking.
The record
- CVE
- CVE-2025-60794
- Published
- Nov 20, 2025
- Updated
- Nov 20, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-316
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 20, 2025CVE publishedPublication date reported by the CVE source.
- Nov 20, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo