CVE-2026-15037

LOWPre-NVD 2.92.9—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 82% 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).

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

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

Improper output neutralization (XML injection) in QDom comment, CDATA, and processing-instruction serialization in Qt XML from 4.0.0 through 6.11 allows untrusted text serialized by an application into those nodes to inject arbitrary XML markup, because the node terminators are not escaped under the default InvalidDataPolicy (AcceptInvalidChars). Fixed in Qt 6.12.

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

Published

July 23, 2026

Last Modified

July 23, 2026

References (1)

Vendor Advisories for CVE-2026-15037(1)

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

Affected Packages

(7 across 4 ecosystems)
Debian:12(2)
PackageVulnerable rangeFixed inDependents
qt6-base6.10.2+dfsg-1 ... 6.9.2+dfsg-4 (89 versions)——
qtbase-opensource-src5.15.10+dfsg-1 ... 5.15.9+dfsg-3 (49 versions)——
Debian:13(2)
PackageVulnerable rangeFixed inDependents
qt6-base6.10.2+dfsg-1 ... 6.9.2+dfsg-4 (36 versions)——
qtbase-opensource-src5.15.15+dfsg-6 ... 5.15.19+dfsg-4 (18 versions)——
Debian:14(2)
PackageVulnerable rangeFixed inDependents
qt6-base6.10.2+dfsg-1 ... 6.9.2+dfsg-4 (34 versions)——
qtbase-opensource-src5.15.15+dfsg-6 ... 5.15.19+dfsg-4 (17 versions)——
Debian:11(1)
PackageVulnerable rangeFixed inDependents
qtbase-opensource-src5.15.10+dfsg-1 ... 5.15.9+dfsg-3 (84 versions)——

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-15037?
CVE-2026-15037 is a low vulnerability published on July 23, 2026. Improper output neutralization (XML injection) in QDom comment, CDATA, and processing-instruction serialization in Qt XML from 4.0.0 through 6.11 allows untrusted text serialized by an application into those nodes to inject arbitrary XML markup, because the node terminators are not escaped under…
When was CVE-2026-15037 disclosed?
CVE-2026-15037 was first published in the National Vulnerability Database on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15037 actively exploited?
CVE-2026-15037 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 81.9% of all scored CVEs.
What is the CVSS score of CVE-2026-15037?
CVE-2026-15037 has a CVSS v3 base score of 2.9 (NVD).
How do I remediate CVE-2026-15037?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15037, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-15037?

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

Start Free Scan →Browse All CVEs