CVE-2026-19037

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreHIGH confidence

Score 4.3 from GitHub Security Advisory (severity: LOW) published 2026-08-06. a secondary CVSS source baseline 4.3; sources differ by 0.0.

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

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

A weakness has been identified in WonderTrader up to 0.9.9. This vulnerability affects the function MatchEngine::update_lob of the file src/WtBtCore/MatchEngine.cpp of the component Internal Limit Order Book Cache Handler. This manipulation causes enforcement of behavioral workflow. Remote exploitation of the attack is possible. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

CVSS v3
4.3
EG Score
4.3(high)
EG Risk
35(Track)
EG Risk 35/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
Severity43% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

August 6, 2026

Last Modified

August 12, 2026

References (5)

Vendor Advisories for CVE-2026-19037(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 47× 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-20 22:55 UTCEPSS rescore
  2. 2026-08-20 20:43 UTCGHSA enrichment
  3. 2026-08-19 20:46 UTCEG score recompute
  4. 2026-08-19 20:46 UTCGHSA enrichment
  5. 2026-08-19 17:03 UTCEPSS rescore
  6. 2026-08-18 20:48 UTCEG score recompute
  7. 2026-08-18 20:48 UTCGHSA enrichment
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-17 20:52 UTCEG score recompute
  10. 2026-08-17 20:52 UTCGHSA enrichment
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-16 20:55 UTCEG score recompute
  13. 2026-08-16 20:55 UTCGHSA enrichment
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 02:14 UTCEPSS rescore
  16. 2026-08-15 20:58 UTCEG score recompute
  17. 2026-08-15 20:58 UTCGHSA enrichment
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-14 21:01 UTCEG score recompute
  20. 2026-08-14 21:01 UTCGHSA enrichment
  21. 2026-08-13 22:00 UTCEPSS rescore
  22. 2026-08-13 21:04 UTCGHSA enrichment
  23. 2026-08-12 21:06 UTCGHSA enrichment
  24. 2026-08-12 15:10 UTCEG score recompute
  25. 2026-08-12 15:10 UTCGHSA enrichment
Show 22 more
  1. 2026-08-12 13:50 UTCEPSS rescore
  2. 2026-08-11 15:13 UTCEG score recompute
  3. 2026-08-11 15:13 UTCGHSA enrichment
  4. 2026-08-11 13:42 UTCEPSS rescore
  5. 2026-08-11 00:00 UTCEPSS rescore
  6. 2026-08-10 15:16 UTCGHSA enrichment
  7. 2026-08-09 15:19 UTCEG score recompute
  8. 2026-08-09 15:19 UTCGHSA enrichment
  9. 2026-08-09 13:46 UTCEPSS rescore
  10. 2026-08-08 16:37 UTCEPSS rescore
  11. 2026-08-08 15:23 UTCEG score recompute
  12. 2026-08-08 15:23 UTCGHSA enrichment
  13. 2026-08-07 15:25 UTCEG score recompute
  14. 2026-08-07 15:25 UTCGHSA enrichment
  15. 2026-08-06 15:29 UTCEG score recompute
  16. 2026-08-06 15:26 UTCNVD updateCVSS v4 → 2.1
  17. 2026-08-06 14:45 UTCEG score recompute
  18. 2026-08-06 14:41 UTCMITRE cvelistV5CVSS v4 → 5.3
  19. 2026-08-06 13:36 UTCEG score recompute
  20. 2026-08-06 13:36 UTCNVD updateCVSS v4 → 2.1
  21. 2026-08-06 13:09 UTCEG score recompute
  22. 2026-08-06 13:08 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-19037?
CVE-2026-19037 is a medium vulnerability published on August 6, 2026. A weakness has been identified in WonderTrader up to 0.9.9. This vulnerability affects the function MatchEngine::update_lob of the file src/WtBtCore/MatchEngine.cpp of the component Internal Limit Order Book Cache Handler. This manipulation causes enforcement of behavioral workflow. Remote…
When was CVE-2026-19037 disclosed?
CVE-2026-19037 was first published in the National Vulnerability Database on August 6, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-19037 actively exploited?
CVE-2026-19037 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 71.6% of all scored CVEs.
What is the CVSS score of CVE-2026-19037?
CVE-2026-19037 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-19037?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-19037, 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-19037

Explore →

Is Your Infrastructure Affected by CVE-2026-19037?

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

Start Free Scan →Browse All CVEs