Approved changes feed: RSS · Atom
cpe:2.3:a:cookies:cookies:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Cookies (4301f8b6-e35b-5ab3-9b4b-384f883f7853) |
|---|---|
| Product | Cookies (de06a950-fd45-5e70-9c3a-cdba2e4182cb) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-88038 |
vulnerable | 2026-09-16 04:34:09.178383 |
cookies vulnerable to Set-Cookie attribute injection via unvalidated domain and path options
MEDIUM (4.8)
cookies is a Node.js library for reading and writing HTTP cookies, used by Koa via ctx.cookies. In versions before 0.9.2 the library validates the cookie name and value against character sets that reject the semicolon separator, but the domain and path options are checked only against a permissive RFC 7230 field-content matcher that allows semicolons, and both are written into the Set-Cookie header unescaped. An application that passes untrusted or request-derived data into the domain or path option can therefore inject additional cookie attributes, overriding SameSite, Secure, HttpOnly, or Domain on the cookies the application issues. This is a Set-Cookie attribute injection issue (CWE-74). The issue is fixed in cookies 0.9.2, which validates domain and path against RFC 6265 character sets. As a workaround, keep domain and path application-set rather than derived from untrusted input.
Published: 2026-09-10T12:11:58.674Z
Updated: 2026-09-10T12:40:30.423Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.