CVE-2026-4018

MEDIUMPre-NVD 6.46.4—
EchelonGraph scoreMEDIUM confidence

Score 6.4 from GitHub Security Advisory published 2026-07-14. a secondary CVSS source baseline 6.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
6.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

TOCTOU Race Condition in specific trace commands of the TraceEvent() system call could allow an attacker with local access and with the PROCMGR_AID_TRACE ability, to cause information disclosure, data tampering or a crash of the QNX Neutrino kernel.

CVSS v3
6.4
EG Score
6.4(medium)
EG Risk
29(Track)
EG Risk 29/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 computed
Severity64% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

July 14, 2026

Last Modified

July 15, 2026

Advisory Details (1)

Auto-updated Jul 15, 2026
No patch confirmed yet.
generic

BlackBerry Public Knowledge Base

https://support.blackberry.com/pkb/s/article/141213

Vendor Advisories for CVE-2026-4018(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 14× in last 7d / 65× 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-08-30 04:16 UTCEG score recompute
  2. 2026-08-30 04:16 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-28 21:41 UTCEPSS rescore
  5. 2026-08-27 21:29 UTCEG score recompute
  6. 2026-08-27 21:29 UTCGHSA enrichment
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-26 13:48 UTCEG score recompute
  10. 2026-08-26 13:48 UTCGHSA enrichment
  11. 2026-08-25 13:49 UTCEPSS rescore
  12. 2026-08-25 11:34 UTCEG score recompute
  13. 2026-08-25 11:34 UTCGHSA enrichment
  14. 2026-08-24 09:22 UTCGHSA enrichment
  15. 2026-08-23 07:09 UTCEG score recompute
  16. 2026-08-23 07:09 UTCGHSA enrichment
  17. 2026-08-23 00:19 UTCEPSS rescore
  18. 2026-08-22 04:56 UTCEG score recompute
  19. 2026-08-22 04:56 UTCGHSA enrichment
  20. 2026-08-21 23:49 UTCEPSS rescore
  21. 2026-08-21 02:43 UTCEG score recompute
  22. 2026-08-21 02:43 UTCGHSA enrichment
  23. 2026-08-20 22:55 UTCEPSS rescore
  24. 2026-08-20 00:30 UTCEG score recompute
  25. 2026-08-20 00:30 UTCGHSA enrichment
Show 63 more
  1. 2026-08-19 17:04 UTCEPSS rescore
  2. 2026-08-18 20:04 UTCEG score recompute
  3. 2026-08-18 20:04 UTCGHSA enrichment
  4. 2026-08-17 13:47 UTCEPSS rescore
  5. 2026-08-17 11:51 UTCEG score recompute
  6. 2026-08-17 11:51 UTCGHSA enrichment
  7. 2026-08-16 14:56 UTCEPSS rescore
  8. 2026-08-16 09:39 UTCEG score recompute
  9. 2026-08-16 09:39 UTCGHSA enrichment
  10. 2026-08-16 02:14 UTCEPSS rescore
  11. 2026-08-15 07:27 UTCEG score recompute
  12. 2026-08-15 07:27 UTCGHSA enrichment
  13. 2026-08-15 01:30 UTCEPSS rescore
  14. 2026-08-14 04:11 UTCEG score recompute
  15. 2026-08-14 04:11 UTCGHSA enrichment
  16. 2026-08-13 01:58 UTCGHSA enrichment
  17. 2026-08-11 23:46 UTCGHSA enrichment
  18. 2026-08-10 21:34 UTCGHSA enrichment
  19. 2026-08-09 19:22 UTCGHSA enrichment
  20. 2026-08-08 17:09 UTCEG score recompute
  21. 2026-08-08 17:09 UTCGHSA enrichment
  22. 2026-08-08 16:37 UTCEPSS rescore
  23. 2026-08-07 14:56 UTCEG score recompute
  24. 2026-08-07 14:56 UTCGHSA enrichment
  25. 2026-08-06 13:47 UTCEPSS rescore
  26. 2026-08-06 12:44 UTCEG score recompute
  27. 2026-08-06 12:44 UTCGHSA enrichment
  28. 2026-08-05 19:17 UTCEPSS rescore
  29. 2026-08-05 10:32 UTCEG score recompute
  30. 2026-08-05 10:32 UTCGHSA enrichment
  31. 2026-08-04 15:10 UTCEPSS rescore
  32. 2026-08-04 10:39 UTCEPSS rescore
  33. 2026-08-04 08:17 UTCEG score recompute
  34. 2026-08-04 08:17 UTCGHSA enrichment
  35. 2026-08-03 10:36 UTCEPSS rescore
  36. 2026-08-03 05:56 UTCGHSA enrichment
  37. 2026-08-02 03:34 UTCEG score recompute
  38. 2026-08-02 03:34 UTCGHSA enrichment
  39. 2026-08-01 04:16 UTCEPSS rescore
  40. 2026-08-01 01:21 UTCGHSA enrichment
  41. 2026-07-30 23:08 UTCEG score recompute
  42. 2026-07-30 23:08 UTCGHSA enrichment
  43. 2026-07-30 16:28 UTCEPSS rescore
  44. 2026-07-29 20:55 UTCGHSA enrichment
  45. 2026-07-28 17:32 UTCGHSA enrichment
  46. 2026-07-27 15:18 UTCEG score recompute
  47. 2026-07-27 15:18 UTCGHSA enrichment
  48. 2026-07-26 14:54 UTCEPSS rescore
  49. 2026-07-26 11:43 UTCEG score recompute
  50. 2026-07-26 11:43 UTCGHSA enrichment
  51. 2026-07-25 14:18 UTCEPSS rescore
  52. 2026-07-24 14:18 UTCEPSS rescore
  53. 2026-07-23 14:18 UTCEPSS rescore
  54. 2026-07-23 03:11 UTCEG score recompute
  55. 2026-07-22 14:08 UTCEPSS rescore
  56. 2026-07-20 17:08 UTCEPSS rescore
  57. 2026-07-16 22:05 UTCGHSA enrichment
  58. 2026-07-16 17:03 UTCEPSS rescore
  59. 2026-07-15 19:53 UTCGHSA enrichment
  60. 2026-07-15 16:57 UTCEPSS rescore
  61. 2026-07-15 16:57 UTCEPSS rescore
  62. 2026-07-14 17:40 UTCMITRE cvelistV5first tracked
  63. 2026-07-14 17:40 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-4018?
CVE-2026-4018 is a medium vulnerability published on July 14, 2026. TOCTOU Race Condition in specific trace commands of the TraceEvent() system call could allow an attacker with local access and with the PROCMGRAIDTRACE ability, to cause information disclosure, data tampering or a crash of the QNX Neutrino kernel.
When was CVE-2026-4018 disclosed?
CVE-2026-4018 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-4018 actively exploited?
CVE-2026-4018 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.0% of all scored CVEs.
What is the CVSS score of CVE-2026-4018?
CVE-2026-4018 has a CVSS v3 base score of 6.4 (NVD).
How do I remediate CVE-2026-4018?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-4018, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-4018

Explore →

Is Your Infrastructure Affected by CVE-2026-4018?

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

Start Free Scan →Browse All CVEs