In FireAMP versions below 2.1.15, a user who holds a role that can edit, create, or run playbooks in Splunk SOAR could run the add listitem action in a Safe Mode playbook while that action is listed as read-only, which could allow for unauthorized changes to file lists. The vulnerability is possible because the FireAMP connector action manifest classifies the add listitem action as read-only even though the action updates file lists. For more information see Manage settings for a playbook in Splunk SOAR (https://help.splunk.com/en/splunk-soar/soar-cloud/build-playbooks/manage-playbooks-and-playbook-settings/manage-settings-for-a-playbook-in-splunk-soar-cloud) in the Splunk documentation.
CVE-2026-76371
Score 2.7 from GitHub Security Advisory (severity: LOW) published 2026-08-20. a secondary CVSS source baseline 2.7; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 2.7
- EG Score
- 2.7(high)
- EG Risk
- 12(Track)EG Risk 12/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity27% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 11%
- KEV
- Not listed
Published
August 19, 2026
Last Modified
August 20, 2026
References (1)
Vendor Advisories for CVE-2026-76371(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 17:35 UTCEG score recompute
- 2026-08-20 17:35 UTCGHSA enrichment
- 2026-08-20 16:35 UTCEG score recompute
- 2026-08-20 16:35 UTCGHSA enrichment
- 2026-08-20 13:16 UTCEG score recompute
- 2026-08-20 13:15 UTCGHSA enrichment
- 2026-08-19 22:21 UTCEG score recompute
- 2026-08-19 21:39 UTCEG score recompute
- 2026-08-19 21:37 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-732
Frequently asked(5)
What is CVE-2026-76371?
When was CVE-2026-76371 disclosed?
Is CVE-2026-76371 actively exploited?
What is the CVSS score of CVE-2026-76371?
How do I remediate CVE-2026-76371?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-76371
Is Your Infrastructure Affected by CVE-2026-76371?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.