A remote code execution issue was discovered in AlienVault USM and OSSIM before 5.5.1.

published 2018-03-14 8y ago modified 2026-06-17 4mo ago also EUVD-2018-19013

cvss: 9.8; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 2.4%; EPSS 2.4% chance of exploitation in 30 days, percentile 84%
public exploits: 0; none known

Patch / fix

fixed in 2

alienvault open_source_security_information_management 5.5.1
alienvault unified_security_management 5.5.1

Is CVE-2018-7279 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

2.44% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	9.8	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	7.5	AV:N/AC:L/Au:N/C:P/I:P/A:P

References

alienvault.com /forums/discussion/17155/alienvault-v5-5-1-hotfix-important-update
vendor-advisory
alienvault.com /forums/discussion/17204/security-advisory-alienvault-v5-5-1-resolves-critical-vulnerability
vendor-advisory

Sources

CVE List CVE-2018-7279
NVD CVE-2018-7279

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.