CVE-2026-9499

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 58% 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
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 6.3Exploit: None knownExposed: 0

A fix is available — apply it.

An out-of-bounds read (buffer over-read) vulnerability exists in QTextCodec::codecForName() in Qt. When the function is called with a QByteArray that is not NUL-terminated (for example, one created with QByteArray::fromRawData()), the codec-name matching routine reads past the end of the supplied buffer. In most cases this results in an incorrect text codec being selected; in the worst case, if the over-read reaches unmapped memory, the process crashes (denial of service). The over-read is bounded by the length of the longest codec-name candidate, and the out-of-bounds bytes are only compared internally against Qt's fixed list of codec names, so no data is disclosed to an attacker. Applications that do not pass non-NUL-terminated QByteArrays to QTextCodec::codecForName() are not exposed. The affected code resides in the Qt5Compat module from Qt 6.0.0 onward, and in Qt Core (qtbase) in Qt 4.x and Qt 5.x.

CVSS v3
6.3
EG Score
6.3(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
Severity63% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
42%
KEV
Not listed

Published

July 21, 2026

Last Modified

July 23, 2026

Vendor Advisories for CVE-2026-9499(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatqt6-main-6.11.1-2.hum12026-07-18redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(7 across 4 ecosystems)
Debian:12(2)
PackageVulnerable rangeFixed inDependents
qt6-5compat6.10.2-1 ... 6.9.2-3 (23 versions)
qtbase-opensource-src5.15.10+dfsg-1 ... 5.15.9+dfsg-3 (49 versions)
Debian:13(2)
PackageVulnerable rangeFixed inDependents
qt6-5compat6.10.2-1 ... 6.9.2-3 (10 versions)
qtbase-opensource-src5.15.15+dfsg-6 ... 5.15.19+dfsg-4 (18 versions)
Debian:14(2)
PackageVulnerable rangeFixed inDependents
qt6-5compat6.10.2-1 ... 6.9.2-3 (9 versions)6.10.2-4
qtbase-opensource-src5.15.15+dfsg-6 ... 5.15.19+dfsg-3 (16 versions)5.15.19+dfsg-4
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.

Data Freshness Timeline

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

Showing the most recent 100 of 116 total refreshes for this CVE.

  1. 2026-08-30 02:18 UTCEG score recompute
  2. 2026-08-30 02:18 UTCVendor advisory
  3. 2026-08-30 02:18 UTCGHSA enrichment
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-28 21:42 UTCEPSS rescore
  6. 2026-08-27 14:25 UTCEPSS rescore
  7. 2026-08-27 11:22 UTCEG score recompute
  8. 2026-08-27 11:22 UTCVendor advisory
  9. 2026-08-27 11:21 UTCGHSA enrichment
  10. 2026-08-26 14:47 UTCEPSS rescore
  11. 2026-08-26 12:43 UTCVendor advisory
  12. 2026-08-26 12:43 UTCGHSA enrichment
  13. 2026-08-25 13:53 UTCEG score recompute
  14. 2026-08-25 13:53 UTCVendor advisory
  15. 2026-08-25 13:53 UTCGHSA enrichment
  16. 2026-08-25 13:49 UTCEPSS rescore
  17. 2026-08-24 15:18 UTCEG score recompute
  18. 2026-08-24 15:18 UTCVendor advisory
  19. 2026-08-24 15:18 UTCGHSA enrichment
  20. 2026-08-24 14:18 UTCEPSS rescore
  21. 2026-08-23 16:46 UTCVendor advisory
  22. 2026-08-23 16:46 UTCGHSA enrichment
  23. 2026-08-22 18:15 UTCEG score recompute
  24. 2026-08-22 18:15 UTCVendor advisory
  25. 2026-08-22 18:14 UTCGHSA enrichment
Show 75 more
  1. 2026-08-21 23:49 UTCEPSS rescore
  2. 2026-08-21 19:43 UTCEG score recompute
  3. 2026-08-21 19:43 UTCGHSA enrichment
  4. 2026-08-20 22:56 UTCEPSS rescore
  5. 2026-08-20 21:12 UTCGHSA enrichment
  6. 2026-08-19 22:41 UTCEG score recompute
  7. 2026-08-19 22:41 UTCGHSA enrichment
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-18 19:33 UTCEG score recompute
  10. 2026-08-18 19:33 UTCGHSA enrichment
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-17 20:56 UTCEG score recompute
  13. 2026-08-17 20:56 UTCGHSA enrichment
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-16 21:09 UTCEG score recompute
  16. 2026-08-16 21:09 UTCGHSA enrichment
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 02:15 UTCEPSS rescore
  19. 2026-08-15 22:38 UTCEG score recompute
  20. 2026-08-15 22:38 UTCGHSA enrichment
  21. 2026-08-15 01:31 UTCEPSS rescore
  22. 2026-08-15 00:06 UTCGHSA enrichment
  23. 2026-08-14 01:35 UTCEG score recompute
  24. 2026-08-14 01:35 UTCGHSA enrichment
  25. 2026-08-13 22:00 UTCEPSS rescore
  26. 2026-08-13 03:03 UTCEG score recompute
  27. 2026-08-13 03:03 UTCGHSA enrichment
  28. 2026-08-12 13:51 UTCEPSS rescore
  29. 2026-08-12 04:32 UTCEG score recompute
  30. 2026-08-12 04:32 UTCGHSA enrichment
  31. 2026-08-11 13:43 UTCEPSS rescore
  32. 2026-08-11 05:56 UTCEG score recompute
  33. 2026-08-11 05:56 UTCGHSA enrichment
  34. 2026-08-11 00:00 UTCEPSS rescore
  35. 2026-08-10 07:25 UTCEG score recompute
  36. 2026-08-10 07:25 UTCGHSA enrichment
  37. 2026-08-09 13:47 UTCEPSS rescore
  38. 2026-08-09 08:54 UTCEG score recompute
  39. 2026-08-09 08:54 UTCGHSA enrichment
  40. 2026-08-08 16:37 UTCEPSS rescore
  41. 2026-08-08 10:22 UTCEG score recompute
  42. 2026-08-08 10:22 UTCGHSA enrichment
  43. 2026-08-07 16:30 UTCEPSS rescore
  44. 2026-08-07 11:51 UTCEG score recompute
  45. 2026-08-07 11:51 UTCGHSA enrichment
  46. 2026-08-06 13:47 UTCEPSS rescore
  47. 2026-08-06 13:20 UTCEG score recompute
  48. 2026-08-06 13:20 UTCGHSA enrichment
  49. 2026-08-05 19:17 UTCEPSS rescore
  50. 2026-08-05 14:48 UTCEG score recompute
  51. 2026-08-05 14:48 UTCGHSA enrichment
  52. 2026-08-04 15:10 UTCEPSS rescore
  53. 2026-08-04 14:01 UTCEG score recompute
  54. 2026-08-04 14:01 UTCGHSA enrichment
  55. 2026-08-04 10:39 UTCEPSS rescore
  56. 2026-08-03 15:24 UTCEG score recompute
  57. 2026-08-03 15:24 UTCGHSA enrichment
  58. 2026-08-03 10:36 UTCEPSS rescore
  59. 2026-08-02 16:53 UTCEG score recompute
  60. 2026-08-02 16:53 UTCGHSA enrichment
  61. 2026-08-02 02:27 UTCEPSS rescore
  62. 2026-08-01 18:22 UTCEG score recompute
  63. 2026-08-01 18:22 UTCGHSA enrichment
  64. 2026-08-01 04:16 UTCEPSS rescore
  65. 2026-07-31 19:51 UTCGHSA enrichment
  66. 2026-07-30 21:19 UTCEG score recompute
  67. 2026-07-30 21:19 UTCGHSA enrichment
  68. 2026-07-30 16:28 UTCEPSS rescore
  69. 2026-07-30 01:30 UTCEPSS rescore
  70. 2026-07-29 22:31 UTCGHSA enrichment
  71. 2026-07-28 23:58 UTCEG score recompute
  72. 2026-07-28 23:58 UTCGHSA enrichment
  73. 2026-07-28 15:37 UTCEPSS rescore
  74. 2026-07-28 01:23 UTCEG score recompute
  75. 2026-07-28 01:23 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-9499?
CVE-2026-9499 is a medium vulnerability published on July 21, 2026. An out-of-bounds read (buffer over-read) vulnerability exists in QTextCodec::codecForName() in Qt. When the function is called with a QByteArray that is not NUL-terminated (for example, one created with QByteArray::fromRawData()), the codec-name matching routine reads past the end of the supplied…
When was CVE-2026-9499 disclosed?
CVE-2026-9499 was first published in the National Vulnerability Database on July 21, 2026, with the most recent update 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-9499 actively exploited?
CVE-2026-9499 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 57.8% of all scored CVEs.
What is the CVSS score of CVE-2026-9499?
CVE-2026-9499 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-9499?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9499, 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-9499

Explore →

Is Your Infrastructure Affected by CVE-2026-9499?

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