CVE-2026-88341

MEDIUMPre-NVD 5.55.5—
EchelonGraph scoreHIGH confidence

Score 5.5 from GitHub Security Advisory published 2026-09-22. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this weekElevated
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: Elevated riskExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

A reachable assertion vulnerability exists in YARA 4.5.8 when loading crafted .yrc compiled rule files. An attacker can provide a malicious file with an invalid arena configuration (num_buffers=0) that triggers an assertion failure in yr_arena_get_ptr(), causing the application to terminate.

CVSS v3
5.5
EG Score
5.5MEDIUMhigh confidence
EG Risk
41
EG Risk 41/100CISA SSVC

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 computed
Severity55% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 22, 2026

Last Modified

September 24, 2026

Advisory Details (2)

Auto-updated Sep 23, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit

commit 0cdff36723cd (NOUIY/yara)

Fix landed in NOUIY/yara commit 0cdff36723cd — awaiting tagged release

https://github.com/NOUIY/yara/commit/0cdff36723cd260243bb2b330bda555693354760
generic

Reachable assertion in yr_arena_get_ptr on crafted .yrc with num_buffers=0 causes SIGABRT (CWE-617) · Issue #2238 · VirusTotal/yara · GitHub

https://github.com/VirusTotal/yara/issues/2238

Vendor Advisories for CVE-2026-88341(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
yara4.2.3-4 ... 4.5.8-1 (16 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
yara4.5.2-1 ... 4.5.8-1 (7 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
yara4.5.2-1 ... 4.5.8-1 (7 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 16× in last 7d / 35× 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.

  1. 2026-10-04 23:22 UTCEPSS rescore
  2. 2026-10-04 15:19 UTCGHSA enrichment
  3. 2026-10-03 15:52 UTCEG score recompute
  4. 2026-10-03 15:52 UTCGHSA enrichment
  5. 2026-10-02 16:29 UTCEG score recompute
  6. 2026-10-02 16:29 UTCGHSA enrichment
  7. 2026-10-01 19:51 UTCEPSS rescore
  8. 2026-10-01 17:04 UTCGHSA enrichment
  9. 2026-09-30 17:41 UTCEG score recompute
  10. 2026-09-30 17:41 UTCGHSA enrichment
  11. 2026-09-30 15:04 UTCEPSS rescore
  12. 2026-09-29 18:18 UTCEG score recompute
  13. 2026-09-29 18:18 UTCGHSA enrichment
  14. 2026-09-28 18:52 UTCEG score recompute
  15. 2026-09-28 18:52 UTCGHSA enrichment
  16. 2026-09-28 13:52 UTCEPSS rescore
  17. 2026-09-27 19:29 UTCEG score recompute
  18. 2026-09-27 19:29 UTCGHSA enrichment
  19. 2026-09-27 13:48 UTCEPSS rescore
  20. 2026-09-26 20:06 UTCEG score recompute
  21. 2026-09-26 20:06 UTCGHSA enrichment
  22. 2026-09-26 15:59 UTCEPSS rescore
  23. 2026-09-25 20:42 UTCGHSA enrichment
  24. 2026-09-24 21:18 UTCGHSA enrichment
  25. 2026-09-24 14:44 UTCEG score recompute
Show 10 more
  1. 2026-09-24 14:44 UTCGHSA enrichment
  2. 2026-09-24 14:04 UTCEPSS rescore
  3. 2026-09-23 17:54 UTCEPSS rescore
  4. 2026-09-23 15:20 UTCGHSA enrichment
  5. 2026-09-23 15:14 UTCEG score recompute▲ 5.50
  6. 2026-09-23 15:14 UTCGHSA enrichment
  7. 2026-09-23 15:14 UTCMITRE cvelistV5CVSS v3 → 5.5 · severity → MEDIUM
  8. 2026-09-22 20:32 UTCNVD update
  9. 2026-09-22 19:53 UTCEG score recompute
  10. 2026-09-22 19:52 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-88341?
CVE-2026-88341 is a medium vulnerability published on September 22, 2026. A reachable assertion vulnerability exists in YARA 4.5.8 when loading crafted .yrc compiled rule files. An attacker can provide a malicious file with an invalid arena configuration (numbuffers=0) that triggers an assertion failure in yrarenagetptr(), causing the application to terminate.
When was CVE-2026-88341 disclosed?
CVE-2026-88341 was first published on September 22, 2026, with the most recent update on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-88341 actively exploited?
CVE-2026-88341 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-88341?
CVE-2026-88341 has a CVSS v3.1 base score of 5.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-88341?
An upstream fix for CVE-2026-88341 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-88341 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-88341

Explore →

Is Your Infrastructure Affected by CVE-2026-88341?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs