Firejailproject Firejail
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in Firejailproject Firejail.
By the Year
In 2026 there have been 0 vulnerabilities in Firejailproject Firejail. Firejail did not have any published security vulnerabilities last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 0 | 0.00 |
| 2025 | 0 | 0.00 |
| 2024 | 0 | 0.00 |
| 2023 | 0 | 0.00 |
| 2022 | 1 | 7.80 |
| 2021 | 1 | 7.00 |
| 2020 | 2 | 0.00 |
| 2019 | 2 | 0.00 |
It may take a day or so for new Firejail vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Firejailproject Firejail Security Vulnerabilities
A Privilege Context Switching issue was discovered in join.c in Firejail 0.9.68
CVE-2022-31214
7.8 - High
- June 09, 2022
A Privilege Context Switching issue was discovered in join.c in Firejail 0.9.68. By crafting a bogus Firejail container that is accepted by the Firejail setuid-root program as a join target, a local attacker can enter an environment in which the Linux user namespace is still the initial user namespace, the NO_NEW_PRIVS prctl is not activated, and the entered mount namespace is under the attacker's control. In this way, the filesystem layout can be adjusted to gain root privileges through execution of available setuid-root binaries such as su or sudo.
Improper Privilege Management
Firejail before 0.9.64.4
CVE-2021-26910
7 - High
- February 08, 2021
Firejail before 0.9.64.4 allows attackers to bypass intended access restrictions because there is a TOCTOU race condition between a stat operation and an OverlayFS mount operation.
TOCTTOU
Firejail through 0.9.62 does not honor the -- end-of-options indicator after the --output option
CVE-2020-17367
- August 11, 2020
Firejail through 0.9.62 does not honor the -- end-of-options indicator after the --output option, which may lead to command injection.
Firejail through 0.9.62 mishandles shell metacharacters during use of the --output or --output-stderr option
CVE-2020-17368
- August 11, 2020
Firejail through 0.9.62 mishandles shell metacharacters during use of the --output or --output-stderr option, which may lead to command injection.
In Firejail before 0.9.60, seccomp filters are writable inside the jail, leading to a lack of intended seccomp restrictions for a process
CVE-2019-12589
- June 03, 2019
In Firejail before 0.9.60, seccomp filters are writable inside the jail, leading to a lack of intended seccomp restrictions for a process that is joined to the jail after a filter has been modified by an attacker.
Firejail before 0.9.60
CVE-2019-12499
- May 31, 2019
Firejail before 0.9.60 allows truncation (resizing to length 0) of the firejail binary on the host by running exploit code inside a firejail sandbox and having the sandbox terminated. To succeed, certain conditions need to be fulfilled: The jail (with the exploit code inside) needs to be started as root, and it also needs to be terminated as root from the host (either by stopping it ungracefully (e.g., SIGKILL), or by using the --shutdown control command). This is similar to CVE-2019-5736.
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for Firejailproject Firejail or by Firejailproject? Click the Watch button to subscribe.
