Nozomi Networks Labs identified a CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') vulnerability in the event notification functionality of KUNBUS piControl in version 2.6.2 that allows a local authenticated attacker to corrupt kernel heap and event-list state and disclose a small amount of adjacent kernel memory, resulting in kernel memory corruption and denial of service, by issuing concurrent crafted requests from multiple threads through the piControl character device.
CVE-2026-13198
This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 99% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- 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
- 5.9
- EG Score
- 5.9(medium)
- EG Risk
- 27(Track)EG Risk 27/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 computedSeverity59% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 1%
- KEV
- Not listed
Published
August 14, 2026
Last Modified
August 14, 2026
References (1)
- prodsec@nozominetworkshttps://www.nozominetworks.com/labs/vulnerability-advisories-cve-2026-13198
Vendor Advisories for CVE-2026-13198(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 19× in last 7d / 19× 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:55 UTCEPSS rescore
- 2026-08-20 07:03 UTCGHSA enrichment
- 2026-08-19 04:55 UTCEG score recompute
- 2026-08-19 04:55 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 02:46 UTCEG score recompute
- 2026-08-18 02:46 UTCGHSA enrichment
- 2026-08-17 00:37 UTCEG score recompute
- 2026-08-17 00:37 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 22:28 UTCGHSA enrichment
- 2026-08-14 20:18 UTCEG score recompute
- 2026-08-14 20:18 UTCGHSA enrichment
- 2026-08-14 19:54 UTCEG score recompute
- 2026-08-14 19:54 UTCGHSA enrichment
- 2026-08-14 16:31 UTCEG score recompute
- 2026-08-14 15:19 UTCEG score recompute
- 2026-08-14 15:18 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-13198?
When was CVE-2026-13198 disclosed?
Is CVE-2026-13198 actively exploited?
What is the CVSS score of CVE-2026-13198?
How do I remediate CVE-2026-13198?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-13198
Is Your Infrastructure Affected by CVE-2026-13198?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.