VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

firejail: vulnerability history, versions and safety

firejail is a package in the Debian ecosystem. Vulert records 36 vulnerabilities for it across 1 release, from Jan 2017 to Jun 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
36 vulnerabilities recorded U36
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all firejail vulnerabilities

Vulert verdict on firejail i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 09 Jun 2022. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 36 vulnerabilities on record across 5 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 36 over 5 years · 0 in the last year i
  • Latest disclosure 09 Jun 2022 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for firejail, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
0.9.64.4-2 U2 Yes Details →

Newest 1 of 1 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 24
  • 2019 4
  • 2020 4
  • 2021 2
  • 2022 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 36 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for firejail

The 5 most severe of 36 vulnerabilities recorded for this package

Search all 36 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Command Injection Vulnerability in Firejail - CVE-2020-17368 9.8 critical 0.9.62-4 11 Aug 2020
Firejail Vulnerability CVE-2017-5206: Bypass of Seccomp-based Sandbox Protection 9.0 critical 0.9.44.4-1 23 Mar 2017
Firejail Sandbox Escape Vulnerability - CVE-2017-5940 8.8 high 0.9.44.6-1 09 Feb 2017
Seccomp Filter Vulnerability in Firejail: Risk of Unauthorized Access 8.8 high 0.9.58.2-2 03 Jun 2019
Local User Sandbox Escape Vulnerability in Firejail 8.8 high 0.9.44.2-3 09 Feb 2017

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About firejail

Is firejail safe to use?

Vulert records 36 vulnerabilities for firejail in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 36 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does firejail have?

36 vulnerabilities are recorded for firejail in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 36 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new firejail vulnerabilities disclosed?

0 vulnerabilities were recorded for firejail in the last 12 months, and the oldest entry in this database dates to 19 Jan 2017. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of firejail are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor firejail for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the firejail version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.