Register | Log in

underscore

Choose email to subscribe with

general

source: underscore (main)
version: 1.13.8~dfsg+~1.13.0-1
maintainer: Debian Javascript Maintainers (archive) (DMD)
uploaders: David Paleino [DMD]
arch: all
std-ver: 4.7.3
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 1.9.1~dfsg-3
oldstable: 1.13.4~dfsg+~1.11.4-3
stable: 1.13.4~dfsg+~1.11.4-3
testing: 1.13.7~dfsg+~1.13.0-6
unstable: 1.13.8~dfsg+~1.13.0-1

versioned links

1.9.1~dfsg-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.13.4~dfsg+~1.11.4-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.13.7~dfsg+~1.13.0-6: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.13.8~dfsg+~1.13.0-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

libjs-underscore
node-underscore

action needed

1 security issue in trixie high

There is 1 open security issue in trixie.

1 important issue:

CVE-2026-27601: Underscore.js is a utility-belt library for JavaScript. Prior to 1.13.8, the _.flatten and _.isEqual functions use recursion without a depth limit. Under very specific conditions, detailed below, an attacker could exploit this in a Denial of Service (DoS) attack by triggering a stack overflow. Untrusted input must be used to create a recursive datastructure, for example using JSON.parse, with no enforced depth limit. The datastructure thus created must be passed to _.flatten or _.isEqual. In the case of _.flatten, the vulnerability can only be exploited if it is possible for a remote client to prepare a datastructure that consists of arrays at all levels AND if no finite depth limit is passed as the second argument to _.flatten. In the case of _.isEqual, the vulnerability can only be exploited if there exists a code path in which two distinct datastructures that were submitted by the same remote client are compared using _.isEqual. For example, if a client submits data that are stored in a database, and the same client can later submit another datastructure that is then compared to the data that were saved in the database previously, OR if a client submits a single request, but its data are parsed twice, creating two non-identical but equivalent datastructures that are then compared. Exceptions originating from the call to _.flatten or _.isEqual, as a result of a stack overflow, are not being caught. This vulnerability is fixed in 1.13.8.

Created: 2026-03-04 Last update: 2026-03-06 23:30

1 security issue in forky high

There is 1 open security issue in forky.

1 important issue:

CVE-2026-27601: Underscore.js is a utility-belt library for JavaScript. Prior to 1.13.8, the _.flatten and _.isEqual functions use recursion without a depth limit. Under very specific conditions, detailed below, an attacker could exploit this in a Denial of Service (DoS) attack by triggering a stack overflow. Untrusted input must be used to create a recursive datastructure, for example using JSON.parse, with no enforced depth limit. The datastructure thus created must be passed to _.flatten or _.isEqual. In the case of _.flatten, the vulnerability can only be exploited if it is possible for a remote client to prepare a datastructure that consists of arrays at all levels AND if no finite depth limit is passed as the second argument to _.flatten. In the case of _.isEqual, the vulnerability can only be exploited if there exists a code path in which two distinct datastructures that were submitted by the same remote client are compared using _.isEqual. For example, if a client submits data that are stored in a database, and the same client can later submit another datastructure that is then compared to the data that were saved in the database previously, OR if a client submits a single request, but its data are parsed twice, creating two non-identical but equivalent datastructures that are then compared. Exceptions originating from the call to _.flatten or _.isEqual, as a result of a stack overflow, are not being caught. This vulnerability is fixed in 1.13.8.

Created: 2026-03-04 Last update: 2026-03-06 23:30

1 security issue in bullseye high

There is 1 open security issue in bullseye.

1 important issue:

CVE-2026-27601: Underscore.js is a utility-belt library for JavaScript. Prior to 1.13.8, the _.flatten and _.isEqual functions use recursion without a depth limit. Under very specific conditions, detailed below, an attacker could exploit this in a Denial of Service (DoS) attack by triggering a stack overflow. Untrusted input must be used to create a recursive datastructure, for example using JSON.parse, with no enforced depth limit. The datastructure thus created must be passed to _.flatten or _.isEqual. In the case of _.flatten, the vulnerability can only be exploited if it is possible for a remote client to prepare a datastructure that consists of arrays at all levels AND if no finite depth limit is passed as the second argument to _.flatten. In the case of _.isEqual, the vulnerability can only be exploited if there exists a code path in which two distinct datastructures that were submitted by the same remote client are compared using _.isEqual. For example, if a client submits data that are stored in a database, and the same client can later submit another datastructure that is then compared to the data that were saved in the database previously, OR if a client submits a single request, but its data are parsed twice, creating two non-identical but equivalent datastructures that are then compared. Exceptions originating from the call to _.flatten or _.isEqual, as a result of a stack overflow, are not being caught. This vulnerability is fixed in 1.13.8.

Created: 2026-03-04 Last update: 2026-03-06 23:30

1 security issue in bookworm high

There is 1 open security issue in bookworm.

1 important issue:

CVE-2026-27601: Underscore.js is a utility-belt library for JavaScript. Prior to 1.13.8, the _.flatten and _.isEqual functions use recursion without a depth limit. Under very specific conditions, detailed below, an attacker could exploit this in a Denial of Service (DoS) attack by triggering a stack overflow. Untrusted input must be used to create a recursive datastructure, for example using JSON.parse, with no enforced depth limit. The datastructure thus created must be passed to _.flatten or _.isEqual. In the case of _.flatten, the vulnerability can only be exploited if it is possible for a remote client to prepare a datastructure that consists of arrays at all levels AND if no finite depth limit is passed as the second argument to _.flatten. In the case of _.isEqual, the vulnerability can only be exploited if there exists a code path in which two distinct datastructures that were submitted by the same remote client are compared using _.isEqual. For example, if a client submits data that are stored in a database, and the same client can later submit another datastructure that is then compared to the data that were saved in the database previously, OR if a client submits a single request, but its data are parsed twice, creating two non-identical but equivalent datastructures that are then compared. Exceptions originating from the call to _.flatten or _.isEqual, as a result of a stack overflow, are not being caught. This vulnerability is fixed in 1.13.8.

Created: 2026-03-04 Last update: 2026-03-06 23:30

lintian reports 2 warnings normal

Lintian reports 2 warnings about this package. You should make the package lintian clean getting rid of them.

Created: 2026-03-07 Last update: 2026-03-07 04:30

debian/patches: 1 patch to forward upstream low

Among the 5 debian patches available in version 1.13.8~dfsg+~1.13.0-1 of the package, we noticed the following issues:

1 patch where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.

Created: 2023-02-26 Last update: 2026-03-07 09:32

testing migrations

excuses:
- Migration status for underscore (1.13.7~dfsg+~1.13.0-6 to 1.13.8~dfsg+~1.13.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ∙ ∙ Autopkgtest for cython/3.1.6+dfsg-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Test triggered, riscv64: Test triggered (failure will be ignored), s390x: Pass
- ∙ ∙ Autopkgtest for liggghts/3.8.0+repack1-14: amd64: Pass, arm64: Regression ♻ (reference ♻), i386: Pass, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Pass, s390x: Pass
- ∙ ∙ Autopkgtest for python3.13/3.13.12-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
- ∙ ∙ Autopkgtest for python3.14/3.14.3-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
- ∙ ∙ Autopkgtest for sqlalchemy/2.0.45+ds1-1: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered (failure will be ignored), s390x: Failed (not a regression) ♻ (reference ♻)
- ∙ ∙ Autopkgtest for swift/2.36.0-8: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Pass, i386: No tests, superficial or marked flaky ♻, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Failed (not a regression) ♻ (reference ♻), s390x: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for underscore/1.13.8~dfsg+~1.13.0-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻, s390x: No tests, superficial or marked flaky ♻
- ∙ ∙ Too young, only 1 of 5 days old
- Additional info (not blocking):
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/u/underscore.html
- ∙ ∙ Reproduced on amd64
- ∙ ∙ Reproduced on arm64
- ∙ ∙ Reproduced on armhf
- ∙ ∙ Reproduced on i386
- ∙ ∙ Reproduced on ppc64el
- Not considered

news

[2026-03-06] Accepted underscore 1.13.8~dfsg+~1.13.0-1 (source) into unstable (Xavier Guimard)
[2026-02-07] underscore 1.13.7~dfsg+~1.13.0-6 MIGRATED to testing (Debian testing watch)
[2026-02-01] Accepted underscore 1.13.7~dfsg+~1.13.0-6 (source) into unstable (Bastien Roucariès) (signed by: Bastien ROUCARIÈS)
[2026-01-26] underscore 1.13.7~dfsg+~1.13.0-5 MIGRATED to testing (Debian testing watch)
[2026-01-23] Accepted underscore 1.13.7~dfsg+~1.13.0-5 (source) into unstable (Bastien Roucariès) (signed by: Bastien ROUCARIÈS)
[2026-01-22] Accepted underscore 1.13.7~dfsg+~1.13.0-4 (source) into unstable (Bastien Roucariès) (signed by: Bastien ROUCARIÈS)
[2026-01-19] Accepted underscore 1.13.7~dfsg+~1.13.0-3 (source) into unstable (Bastien Roucariès) (signed by: Bastien ROUCARIÈS)
[2026-01-19] Accepted underscore 1.13.7~dfsg+~1.13.0-2 (source) into unstable (Bastien Roucariès) (signed by: Bastien ROUCARIÈS)
[2026-01-17] Accepted underscore 1.13.7~dfsg+~1.13.0-1 (source) into unstable (Bastien Roucariès) (signed by: Bastien ROUCARIÈS)
[2023-01-07] underscore 1.13.4~dfsg+~1.11.4-3 MIGRATED to testing (Debian testing watch)
[2023-01-02] Accepted underscore 1.13.4~dfsg+~1.11.4-3 (source) into unstable (Yadd) (signed by: Xavier Guimard)
[2022-11-07] underscore 1.13.4~dfsg+~1.11.4-2 MIGRATED to testing (Debian testing watch)
[2022-11-02] Accepted underscore 1.13.4~dfsg+~1.11.4-2 (source) into unstable (Yadd) (signed by: Xavier Guimard)
[2022-09-07] underscore 1.13.4~dfsg+~1.11.4-1 MIGRATED to testing (Debian testing watch)
[2022-09-04] Accepted underscore 1.13.4~dfsg+~1.11.4-1 (source) into unstable (Yadd) (signed by: Xavier Guimard)
[2022-05-01] underscore 1.13.3~dfsg+~1.11.4-1 MIGRATED to testing (Debian testing watch)
[2022-04-26] Accepted underscore 1.13.3~dfsg+~1.11.4-1 (source) into unstable (Yadd) (signed by: Xavier Guimard)
[2022-02-01] underscore 1.13.2~dfsg-2 MIGRATED to testing (Debian testing watch)
[2022-01-27] Accepted underscore 1.13.2~dfsg-2 (source) into unstable (Yadd) (signed by: Xavier Guimard)
[2022-01-19] Accepted underscore 1.13.2~dfsg-1 (source) into experimental (Yadd) (signed by: Xavier Guimard)
[2021-09-20] underscore 1.9.1~dfsg-4 MIGRATED to testing (Debian testing watch)
[2021-09-15] Accepted underscore 1.9.1~dfsg-4 (source) into unstable (Jelmer Vernooĳ) (signed by: Jelmer Vernooij)
[2021-04-09] underscore 1.9.1~dfsg-3 MIGRATED to testing (Debian testing watch)
[2021-04-05] Accepted underscore 1.9.1~dfsg-1+deb10u1 (source all) into proposed-updates->stable-new, proposed-updates (Debian FTP Masters) (signed by: Xavier Guimard)
[2021-04-01] Accepted underscore 1.9.1~dfsg-1+deb10u1 (source all) into stable->embargoed, stable (Debian FTP Masters) (signed by: Xavier Guimard)
[2021-03-31] Accepted underscore 1.8.3~dfsg-1+deb9u1 (source all) into oldstable (Yadd) (signed by: Xavier Guimard)
[2021-03-31] Accepted underscore 1.9.1~dfsg-3 (source) into unstable (Yadd) (signed by: Xavier Guimard)
[2021-03-30] Accepted underscore 1.9.1~dfsg-2 (source) into unstable (Yadd) (signed by: Xavier Guimard)
[2019-03-06] underscore 1.9.1~dfsg-1 MIGRATED to testing (Debian testing watch)
[2019-02-23] Accepted underscore 1.9.1~dfsg-1 (source) into unstable (Jonas Smedegaard)

1
2

bugs [bug history graph]

all: 0

links

homepage
lintian (0, 2)
buildd: logs, reproducibility
popcon
browse source code
edit tags
other distros
security tracker
debian patches
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 1.13.7~dfsg+~1.13.0-6

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