Debian Package Tracker
Register | Log in
Subscribe

node-cookies

Cookies, optionally signed using Keygrip - Node.js module

Choose email to subscribe with

general
  • source: node-cookies (main)
  • version: 0.9.2+~0.9.2-1
  • maintainer: Debian Javascript Maintainers (archive) (DMD)
  • uploaders: Yadd [DMD]
  • arch: all
  • std-ver: 4.7.4
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • o-o-stable: 0.8.0-2
  • oldstable: 0.8.0+~0.7.7-1
  • stable: 0.8.0+~0.7.7-1
  • testing: 0.9.1+~0.9.2-1
  • unstable: 0.9.2+~0.9.2-1
versioned links
  • 0.8.0-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 0.8.0+~0.7.7-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 0.9.1+~0.9.2-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 0.9.2+~0.9.2-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • node-cookies
action needed
1 security issue in forky high

There is 1 open security issue in forky.

1 important issue:
  • CVE-2026-88038: 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.
Created: 2026-09-11 Last update: 2026-09-14 00:00
1 security issue in bookworm high

There is 1 open security issue in bookworm.

1 important issue:
  • CVE-2026-88038: 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.
Created: 2026-09-11 Last update: 2026-09-14 00:00
1 low-priority security issue in trixie low

There is 1 open security issue in trixie.

1 issue left for the package maintainer to handle:
  • CVE-2026-88038: (needs triaging) 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.

You can find information about how to handle this issue in the security team's documentation.

Created: 2026-09-11 Last update: 2026-09-14 00:00
testing migrations
  • excuses:
    • Migration status for node-cookies (0.9.1+~0.9.2-1 to 0.9.2+~0.9.2-1): Waiting for test results or another package, or too young (no action required now - check later)
    • Issues preventing migration:
    • ∙ ∙ Autopkgtest for node-client-sessions/0.8.0+~0.8.7-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: Test triggered, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • ∙ ∙ Autopkgtest for node-cookies/0.9.2+~0.9.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
    • ∙ ∙ Autopkgtest for node-express/5.2.1+~cs12.3.9-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
    • ∙ ∙ Too young, only 1 of 5 days old
    • Additional info (not blocking):
    • ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/n/node-cookies.html
    • ∙ ∙ Reproduced on amd64 - info
    • ∙ ∙ Reproduced on arm64 - info
    • ∙ ∙ Reproduced on armhf - info
    • ∙ ∙ Reproduced on i386 - info
    • Not considered
news
[rss feed]
  • [2026-09-13] Accepted node-cookies 0.9.2+~0.9.2-1 (source) into unstable (Xavier Guimard)
  • [2026-03-24] node-cookies 0.9.1+~0.9.2-1 MIGRATED to testing (Debian testing watch)
  • [2026-03-21] Accepted node-cookies 0.9.1+~0.9.2-1 (source) into unstable (Xavier Guimard)
  • [2021-11-28] node-cookies 0.8.0+~0.7.7-1 MIGRATED to testing (Debian testing watch)
  • [2021-11-26] Accepted node-cookies 0.8.0+~0.7.7-1 (source) into unstable (Yadd) (signed by: Xavier Guimard)
  • [2019-12-24] node-cookies 0.8.0-2 MIGRATED to testing (Debian testing watch)
  • [2019-12-21] Accepted node-cookies 0.8.0-2 (source) into unstable (Xavier Guimard)
  • [2019-11-16] node-cookies 0.8.0-1 MIGRATED to testing (Debian testing watch)
  • [2019-11-13] Accepted node-cookies 0.8.0-1 (source) into unstable (Xavier Guimard)
  • [2019-08-09] node-cookies 0.5.0-3 MIGRATED to testing (Debian testing watch)
  • [2019-08-04] Accepted node-cookies 0.5.0-3 (source) into unstable (Xavier Guimard)
  • [2019-07-09] node-cookies 0.5.0-2 MIGRATED to testing (Debian testing watch)
  • [2019-05-24] Accepted node-cookies 0.5.0-2 (source) into unstable (Graham Inggs)
  • [2014-09-23] node-cookies 0.5.0-1 MIGRATED to testing (Britney)
  • [2014-09-12] Accepted node-cookies 0.5.0-1 (source all) into unstable (Andrew Kelley) (signed by: Jérémy Lal)
  • [2014-08-02] node-cookies 0.4.1-1 MIGRATED to testing (Britney)
bugs [bug history graph]
  • all: 0
links
  • homepage
  • lintian
  • buildd: logs, reproducibility
  • popcon
  • browse source code
  • other distros
  • security tracker
  • debci
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 0.9.1+~0.9.2-1

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing