squirrel3 - Debian Package Tracker

general

source: squirrel3 (main)
version: 3.1-8.4
maintainer: Fabian Wolff (DMD) (DM)
arch: any
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: 3.1-8
stable: 3.1-8.2
testing: 3.1-8.3
unstable: 3.1-8.4

versioned links

3.1-8: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.1-8.2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.1-8.3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.1-8.4: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

libsquirrel-dev
libsquirrel3-0
squirrel3

action needed

A new upstream version is available: 3.2 high

A new upstream version 3.2 is available, you should consider packaging it.

Created: 2026-04-11 Last update: 2026-04-13 07:02

5 security issues in sid high

There are 5 open security issues in sid.

5 important issues:

CVE-2026-2659: A vulnerability was determined in Squirrel up to 3.2. Affected by this vulnerability is the function SQFuncState::PopTarget of the file src/squirrel/squirrel/sqfuncstate.cpp. Executing a manipulation of the argument _target_stack can lead to out-of-bounds read. It is possible to launch the attack on the local host. The exploit has been publicly disclosed and may be utilized. The project was informed of the problem early through an issue report but has not responded yet.
CVE-2026-2661: A security flaw has been discovered in Squirrel up to 3.2. This affects the function SQObjectPtr::operator in the library squirrel/sqobject.h. The manipulation results in heap-based buffer overflow. The attack needs to be approached locally. The exploit has been released to the public and may be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.
CVE-2026-3388: A vulnerability was found in Squirrel up to 3.2. This affects the function SQCompiler::Factor/SQCompiler::UnaryOP of the file squirrel/sqcompiler.cpp. Performing a manipulation results in uncontrolled recursion. The attack needs to be approached locally. The exploit has been made public and could be used. The project was informed of the problem early through an issue report but has not responded yet.
CVE-2026-3389: A vulnerability was determined in Squirrel up to 3.2. This vulnerability affects the function sqstd_rex_newnode in the library sqstdlib/sqstdrex.cpp. Executing a manipulation can lead to null pointer dereference. The attack can only be executed locally. The exploit has been publicly disclosed and may be utilized. The project was informed of the problem early through an issue report but has not responded yet.
CVE-2021-41556: sqclass.cpp in Squirrel through 2.2.5 and 3.x through 3.1 allows an out-of-bounds read (in the core interpreter) that can lead to Code Execution. If a victim executes an attacker-controlled squirrel script, it is possible for the attacker to break out of the squirrel script sandbox even if all dangerous functionality such as File System functions has been disabled. An attacker might abuse this bug to target (for example) Cloud services that allow customization via SquirrelScripts, or distribute malware through video games that embed a Squirrel Engine.

Created: 2022-07-04 Last update: 2026-04-11 16:01

5 security issues in forky high

There are 5 open security issues in forky.

5 important issues:

CVE-2026-2659: A vulnerability was determined in Squirrel up to 3.2. Affected by this vulnerability is the function SQFuncState::PopTarget of the file src/squirrel/squirrel/sqfuncstate.cpp. Executing a manipulation of the argument _target_stack can lead to out-of-bounds read. It is possible to launch the attack on the local host. The exploit has been publicly disclosed and may be utilized. The project was informed of the problem early through an issue report but has not responded yet.
CVE-2026-2661: A security flaw has been discovered in Squirrel up to 3.2. This affects the function SQObjectPtr::operator in the library squirrel/sqobject.h. The manipulation results in heap-based buffer overflow. The attack needs to be approached locally. The exploit has been released to the public and may be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.
CVE-2026-3388: A vulnerability was found in Squirrel up to 3.2. This affects the function SQCompiler::Factor/SQCompiler::UnaryOP of the file squirrel/sqcompiler.cpp. Performing a manipulation results in uncontrolled recursion. The attack needs to be approached locally. The exploit has been made public and could be used. The project was informed of the problem early through an issue report but has not responded yet.
CVE-2026-3389: A vulnerability was determined in Squirrel up to 3.2. This vulnerability affects the function sqstd_rex_newnode in the library sqstdlib/sqstdrex.cpp. Executing a manipulation can lead to null pointer dereference. The attack can only be executed locally. The exploit has been publicly disclosed and may be utilized. The project was informed of the problem early through an issue report but has not responded yet.
CVE-2021-41556: sqclass.cpp in Squirrel through 2.2.5 and 3.x through 3.1 allows an out-of-bounds read (in the core interpreter) that can lead to Code Execution. If a victim executes an attacker-controlled squirrel script, it is possible for the attacker to break out of the squirrel script sandbox even if all dangerous functionality such as File System functions has been disabled. An attacker might abuse this bug to target (for example) Cloud services that allow customization via SquirrelScripts, or distribute malware through video games that embed a Squirrel Engine.

Created: 2025-08-09 Last update: 2026-04-11 16:01

The VCS repository is not up to date, push the missing commits. high

vcswatch reports that the current version of the package is not in its VCS.
Either you need to push your commits and/or your tags, or the information about the package's VCS are out of date. A common cause of the latter issue when using the Git VCS is not specifying the correct branch when the packaging is not in the default one (remote HEAD branch), which is usually "master" but can be modified in salsa.debian.org in the project's general settings with the "Default Branch" field). Alternatively the Vcs-Git field in debian/control can contain a "-b <branch-name>" suffix to indicate what branch is used for the Debian packaging.

Created: 2024-05-07 Last update: 2026-04-11 15:01

Multiarch hinter reports 1 issue(s) normal

There are issues with the multiarch metadata for this package.

libsquirrel-dev could be marked Multi-Arch: same

Created: 2026-01-22 Last update: 2026-04-13 09:01

1 open merge request in Salsa normal

There is 1 open merge request for this package on Salsa. You should consider reviewing and/or merging these merge requests.

Created: 2026-04-11 Last update: 2026-04-11 15:01

debian/patches: 2 patches to forward upstream low

Among the 4 debian patches available in version 3.1-8.4 of the package, we noticed the following issues:

2 patches 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: 2024-05-20 Last update: 2026-04-11 21:01

5 low-priority security issues in trixie low

There are 5 open security issues in trixie.

5 issues left for the package maintainer to handle:

CVE-2026-2659: (needs triaging) A vulnerability was determined in Squirrel up to 3.2. Affected by this vulnerability is the function SQFuncState::PopTarget of the file src/squirrel/squirrel/sqfuncstate.cpp. Executing a manipulation of the argument _target_stack can lead to out-of-bounds read. It is possible to launch the attack on the local host. The exploit has been publicly disclosed and may be utilized. The project was informed of the problem early through an issue report but has not responded yet.
CVE-2026-2661: (needs triaging) A security flaw has been discovered in Squirrel up to 3.2. This affects the function SQObjectPtr::operator in the library squirrel/sqobject.h. The manipulation results in heap-based buffer overflow. The attack needs to be approached locally. The exploit has been released to the public and may be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.
CVE-2026-3388: (needs triaging) A vulnerability was found in Squirrel up to 3.2. This affects the function SQCompiler::Factor/SQCompiler::UnaryOP of the file squirrel/sqcompiler.cpp. Performing a manipulation results in uncontrolled recursion. The attack needs to be approached locally. The exploit has been made public and could be used. The project was informed of the problem early through an issue report but has not responded yet.
CVE-2026-3389: (needs triaging) A vulnerability was determined in Squirrel up to 3.2. This vulnerability affects the function sqstd_rex_newnode in the library sqstdlib/sqstdrex.cpp. Executing a manipulation can lead to null pointer dereference. The attack can only be executed locally. The exploit has been publicly disclosed and may be utilized. The project was informed of the problem early through an issue report but has not responded yet.
CVE-2021-41556: (needs triaging) sqclass.cpp in Squirrel through 2.2.5 and 3.x through 3.1 allows an out-of-bounds read (in the core interpreter) that can lead to Code Execution. If a victim executes an attacker-controlled squirrel script, it is possible for the attacker to break out of the squirrel script sandbox even if all dangerous functionality such as File System functions has been disabled. An attacker might abuse this bug to target (for example) Cloud services that allow customization via SquirrelScripts, or distribute malware through video games that embed a Squirrel Engine.

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

Created: 2023-10-22 Last update: 2026-04-11 16:01

testing migrations

excuses:
- Migration status for squirrel3 (3.1-8.3 to 3.1-8.4): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- ∙ ∙ Too young, only 2 of 5 days old
- Additional info (not blocking):
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/s/squirrel3.html
- ∙ ∙ Reproduced on amd64
- ∙ ∙ Reproduced on arm64
- ∙ ∙ Reproduced on armhf
- ∙ ∙ Reproducibility check waiting for results on i386
- ∙ ∙ Reproducibility check waiting for results on ppc64el
- Not considered

news

[rss feed]

[2026-04-11] Accepted squirrel3 3.1-8.4 (source) into unstable (Alexandre Detiste)
[2025-11-16] squirrel3 3.1-8.3 MIGRATED to testing (Debian testing watch)
[2025-11-11] Accepted squirrel3 3.1-8.3 (source) into unstable (Adrian Bunk)
[2024-05-25] squirrel3 3.1-8.2 MIGRATED to testing (Debian testing watch)
[2024-05-20] Accepted squirrel3 3.1-8.2 (source) into unstable (Matthias Geiger) (signed by: Pierre-Elliott Bécue)
[2024-05-06] Accepted squirrel3 3.1-8.1 (source) into unstable (Matthias Geiger) (signed by: Pierre-Elliott Bécue)
[2021-11-23] squirrel3 REMOVED from testing (Debian testing watch)
[2019-08-06] squirrel3 3.1-8 MIGRATED to testing (Debian testing watch)
[2019-08-01] Accepted squirrel3 3.1-8 (source) into unstable (Fabian Wolff)
[2019-03-31] squirrel3 3.1-7 MIGRATED to testing (Debian testing watch)
[2019-03-21] Accepted squirrel3 3.1-7 (source) into unstable (Fabian Wolff) (signed by: Andreas Tille)
[2019-03-19] Accepted squirrel3 3.1-6 (source) into unstable (Fabian Wolff) (signed by: Andreas Tille)
[2017-09-24] squirrel3 3.1-5 MIGRATED to testing (Debian testing watch)
[2017-09-17] Accepted squirrel3 3.1-5 (source amd64) into unstable (Fabian Wolff)
[2016-08-02] squirrel3 3.1-4 MIGRATED to testing (Debian testing watch)
[2016-07-27] Accepted squirrel3 3.1-4 (source) into unstable (Fabian Wolff) (signed by: Daniel Stender)
[2016-07-06] squirrel3 3.1-3 MIGRATED to testing (Debian testing watch)
[2016-06-30] Accepted squirrel3 3.1-3 (source) into unstable (Fabian Wolff) (signed by: Daniel Stender)
[2016-04-25] Accepted squirrel3 3.1-2 (source amd64) into unstable (Fabian Wolff) (signed by: Daniel Stender)
[2016-04-08] Accepted squirrel3 3.1-1 (source amd64) into unstable, unstable (Fabian Wolff) (signed by: Daniel Stender)

bugs [bug history graph]

all: 5
RC: 0
I&N: 5
M&W: 0
F&P: 0
patch: 0

links

homepage
lintian
buildd: logs, reproducibility, cross
popcon
browse source code
other distros
security tracker
debian patches

ubuntu

[Information about Ubuntu for Debian Developers]

version: 3.1-8.3