CVE-2017-18367: libseccomp-golang 0.9.0 and earlier incorrectly generates BPFs that OR multiple arguments rather than ANDing t

Q: How do I fix CVE-2017-18367?

libseccomp-golang: upgrade to newer than 0.9.0. Exact commands for each OS are on this page.

Q: Is CVE-2017-18367 being exploited?

CVE-2017-18367 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2017-18367 affect?

CVE-2017-18367 affects libseccomp-golang. Severity is high (CVSS 7.5). libseccomp-golang 0.9.0 and earlier incorrectly generates BPFs that OR multiple arguments rather than ANDing them. A process running under a restrictive seccomp filter that specified multiple syscall arguments could bypass intended access r

Q: How urgent is CVE-2017-18367?

Priority 52/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 7.5REMOTEUPGRADE

CVE-2017-18367 is a high-severity flaw (CVSS 7.5) affecting libseccomp-golang. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

libseccomp-golang 0.9.0 and earlier incorrectly generates BPFs that OR multiple arguments rather than ANDing them. A process running under a restrictive seccomp filter that specified multiple syscall arguments could bypass intended access restrictions by specifying a single matching argument.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.4% (top 16%)
CISA exploited list	No
Weakness	CWE-20
Published	2019-04-24
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: libseccomp-golang project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2019-04-24 21:29 UTCPublished CVE record published
2026-06-17 01:12 UTCUpdated Record last modified

libseccomp-golang project libseccomp-golang UPGRADE

Affected: <= 0.9.0

Fixed in: newer than 0.9.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy libseccomp-golang || rpm -q libseccomp-golang || libseccomp-golang --version

2. UPGRADE to newer than 0.9.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade libseccomp-golang

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade libseccomp-golang

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-18367?

libseccomp-golang: upgrade to newer than 0.9.0. Exact commands for each OS are on this page.

Is CVE-2017-18367 being exploited?

CVE-2017-18367 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-18367 affect?

CVE-2017-18367 affects libseccomp-golang. Severity is high (CVSS 7.5). libseccomp-golang 0.9.0 and earlier incorrectly generates BPFs that OR multiple arguments rather than ANDing them. A process running under a restrictive seccomp filter that specified multiple syscall arguments could bypass intended access r

How urgent is CVE-2017-18367?

Priority 52/100. High severity; Remotely exploitable, no login, no user action

Software pages

Go (Golang) vulnerabilities

References

← Back to latest CVEs