How severe is CVE-2017-18367?

CVE-2017-18367 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2017-18367?

CVE-2017-18367 affects the following packages: github.com/seccomp/libseccomp-golang (Go). Ecosystems affected: Go.

How do I fix CVE-2017-18367?

Update github.com/seccomp/libseccomp-golang to 0.9.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-18367 is resolved across your whole dependency graph.

How do I detect CVE-2017-18367 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/seccomp/libseccomp-golang, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2017-18367 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2017-18367 actively exploited in the wild?

No public exploit code has been indexed for CVE-2017-18367 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2017-18367?

CVE-2017-18367 has an EPSS (Exploit Prediction Scoring System) score of 2.4%, placing it in the 84th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2017-18367?

CVE-2017-18367 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2017-18367 published, and has it been updated?

CVE-2017-18367 was published on April 24, 2019 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

HIGH severity

CVE-2017-18367 — libseccomp-golang

HIGHFix: seccomp/libseccomp-golang@06e7a29

CVE-2017-18367 is a high-severity (CVSS 7.5) Improper Input Validation vulnerability in github.com/seccomp/libseccomp-golang. A fix is available for github.com/seccomp/libseccomp-golang — see the affected versions and patch details below.

Improper Input Validation in libseccomp-golang

Also known asGHSA-58v3-j75h-xr49GO-2020-0007

Published

Apr 24, 2019

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs84th percentile — riskier than 84% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2017-18367 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

🐹github.com/seccomp/libseccomp-golang

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/seccomp/libseccomp-golang`	all versions	0.9.1`go get github.com/seccomp/libseccomp-golang@v0.9.1`

Affected Products

1 product · 1 configurations

Application

libseccomp-golanglibseccomp-golang_project

≤ 0.9.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/seccomp/libseccomp-golang, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/seccomp/libseccomp-golang to 0.9.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-18367 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

This issue may affect OpenShift Container Platform 3.x and 4.x if you are providing a custom Seccomp profile using Security Context Constraints [1]. The custom Seccomp profile would need to specify multiple arguments, such as below, from [2]. { "names": [ "socketcall" ], "action": "SCMP_ACT_ALLOW", "args":…

Product	Fixed in	Advisory
Red Hat OpenShift Container Platform 3.11	`atomic-openshift-0:3.11.232-1.git.0.a5bc32f.el7`	RHSA-2020:2479
Red Hat OpenShift Container Platform 4.1	`openshift-0:4.1.27-201912021146.git.0.a40116f.el7`	RHSA-2019:4087
Red Hat OpenShift Container Platform 4.1	`openshift4/ose-cli:v4.1.27-201912030019`	RHSA-2019:4090

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2017-18367 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

None

Raw vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

CWE Classification

CWE-20Improper Input Validation

Weaponization

No known public exploit tooling found.

OpenSSF Scorecard

Package health score

libseccomp-golang

6.2/10

Code-Review10/10

Maintained10/10

Branch-ProtectionN/A

Assessed Oct 5, 2026

Timeline

Disclosed

Apr 24, 2019

Last updated

Jul 8, 2026

Identifiers

CVE-2017-18367

GHSA-58v3-j75h-xr49

GO-2020-0007

References

Advisoryaccess.redhat.com Advisoryaccess.redhat.com Advisorynvd.nist.gov Fixopenwall.com Fixgithub.com Fixgithub.com Weblists.debian.org Webusn.ubuntu.com Webusn.ubuntu.com

Related vulnerabilities

This CVE is high severity; 2 of 8 other CVEs with CWE-20 are rated as high or higher (top: high).

CVE-2026-61794CVE-2026-81875CVE-2026-81876CVE-2026-61793GHSA-2xmm-m4wv-3fjhCVE-2026-56831CVE-2026-54529GHSA-cc9r-2j5m-2m83Browse all CWE-20

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedJul 8, 2026

CVE-2017-18367 — libseccomp-golang

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2017-18367 in your dependencies?