How severe is CVE-2017-5206?

CVE-2017-5206 has a CVSS 3.x base score of 9.0, rated critical severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2017-5206 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (78th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2017-5206?

CVE-2017-5206 affects Firejail Project Firejail. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2017-5206?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2017-5206 published?

CVE-2017-5206 was published on 2017-03-23 and last updated on 2026-06-17.

CVE-2017-5206

CVE-2017-5206 is a critical-severity vulnerability in Firejail Project Firejail with a CVSS 3.x base score of 9.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Critical (CVSS 3.x base score 9.0)
CVSS v2: 6.8
EPSS exploit prediction: 2% (78th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Firejail Project Firejail
Published: 2017-03-23
Last modified: 2026-06-17

Description

Firejail before 0.9.44.4, when running on a Linux kernel before 4.8, allows context-dependent attackers to bypass a seccomp-based sandbox protection mechanism via the --allow-debuggers argument.

Frequently asked questions

What is CVE-2017-5206?: Firejail before 0.9.44.4, when running on a Linux kernel before 4.8, allows context-dependent attackers to bypass a seccomp-based sandbox protection mechanism via the --allow-debuggers argument.
How severe is CVE-2017-5206?: CVE-2017-5206 has a CVSS 3.x base score of 9.0, rated critical severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2017-5206 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (78th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-5206?: CVE-2017-5206 affects Firejail Project Firejail. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2017-5206?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2017-5206 published?: CVE-2017-5206 was published on 2017-03-23 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:firejail_project:firejail:*:*:*:*:*:*:*:*

More vulnerabilities in Firejail Project Firejail

CVE-2020-17368 — Critical (CVSS 9.8): Firejail through 0.9.62 mishandles shell metacharacters during use of the --output or --output-stderr option, which may…
CVE-2019-12589 — High (CVSS 8.8): In Firejail before 0.9.60, seccomp filters are writable inside the jail, leading to a lack of intended seccomp…
CVE-2017-5940 — High (CVSS 8.8): Firejail before 0.9.44.6 and 0.9.38.x LTS before 0.9.38.10 LTS does not comprehensively address dotfile cases during…
CVE-2017-5180 — High (CVSS 8.8): Firejail before 0.9.44.4 and 0.9.38.x LTS before 0.9.38.8 LTS does not consider the .Xauthority case during its attempt…
CVE-2016-9016 — High (CVSS 8.8): Firejail 0.9.38.4 allows local users to execute arbitrary commands outside of the sandbox via a crafted TIOCSTI ioctl…
CVE-2019-12499 — High (CVSS 8.1): Firejail before 0.9.60 allows truncation (resizing to length 0) of the firejail binary on the host by running exploit…

All CVEs affecting Firejail Project Firejail →