Cookie disclosure via prototype-polluting domain key
Published Jul 1, 2023 · Updated Aug 27, 2025
Prototype pollution in Salesforce tough-cookie before 4.1.3 allows attackers to expose stored cookies through a crafted domain value. MemoryCookieStore indexes cookies in ordinary JavaScript objects, so a proto domain key writes cookie paths into Object.prototype. Exposure requires a CookieJar with rejectPublicSuffixes=false and the default MemoryCookieStore, and it lasts only for the running process.
Summary
What happened
Prototype pollution in Salesforce tough-cookie before 4.1.3 allows attackers to expose stored cookies through a crafted domain value. MemoryCookieStore indexes cookies in ordinary JavaScript objects, so a proto domain key writes cookie paths into Object.prototype. Exposure requires a CookieJar with rejectPublicSuffixes=false and the default MemoryCookieStore, and it lasts only for the running process.
The record
- CVE
- CVE-2023-26136
- Published
- Jul 1, 2023
- Updated
- Aug 27, 2025
- Vendor
- Salesforce
- Product
- tough-cookie
- Classifications
- CWE-1321
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 1, 2023CVE publishedPublication date reported by the CVE source.
- Aug 27, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <4.1.3
What conditions does exploitation require?
What is affected?
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
- GitHub issue 282 proof of conceptproof of concept · demonstrated
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