CVE-2026-95509

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (24th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-88732 (ENISA EUVD) · GHSA-5q52-pjpv-x8mh (GitHub Security Advisories)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Strings optimized for Latin-1 displaying Latin-1 characters cause incorrect String.arg() formatting by an incorrect buffer size calculation, causing out-of-bounds reading.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
55
EG Risk 55/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
24th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 29, 2026

Last Modified

September 30, 2026

Advisory Details (1)

Auto-updated Sep 29, 2026
Patch available.
Web page

List of known vulnerabilities in Qt products - Qt Wiki

https://wiki.qt.io/List_of_known_vulnerabilities_in_Qt_products#CVE-2026-95509:

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatqt5-main-5.15.18-3.1.hum12026-10-12redhat
redhatqt6-main-6.11.2-1.1.hum12026-10-12redhat

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.

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 70× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  3. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  4. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  5. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  6. 2026-10-27 21:12 UTCEG score recompute
  7. 2026-10-27 21:12 UTCVendor advisory
  8. 2026-10-27 21:12 UTCGHSA enrichmentGHSA-5q52-pjpv-x8mh · GitHub severity HIGH
  9. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  10. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  11. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  12. 2026-10-25 13:48 UTCEG score recompute
  13. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  14. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  15. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  16. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  17. 2026-10-20 17:45 UTCEG score recompute
  18. 2026-10-20 17:45 UTCGHSA enrichmentGHSA-5q52-pjpv-x8mh · GitHub severity HIGH
  19. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  20. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  21. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  22. 2026-10-18 02:57 UTCEG score recompute
  23. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  24. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  25. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
Show 66 more
  1. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  2. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  3. 2026-10-13 04:12 UTCEG score recompute
  4. 2026-10-13 04:12 UTCGHSA enrichmentGHSA-5q52-pjpv-x8mh · GitHub severity HIGH
  5. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  6. 2026-10-12 14:41 UTCEG score recompute
  7. 2026-10-12 04:21 UTCGHSA enrichmentGHSA-5q52-pjpv-x8mh · GitHub severity HIGH
  8. 2026-10-11 19:11 UTCEG score recompute
  9. 2026-10-11 16:42 UTCGHSA enrichmentGHSA-5q52-pjpv-x8mh · GitHub severity HIGH
  10. 2026-10-11 16:27 UTCEG score recompute
  11. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  12. 2026-10-11 13:39 UTCEG score recompute
  13. 2026-10-11 05:14 UTCEG score recompute
  14. 2026-10-11 05:14 UTCGHSA enrichmentGHSA-5q52-pjpv-x8mh · GitHub severity HIGH
  15. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  16. 2026-10-10 17:45 UTCGHSA enrichmentGHSA-5q52-pjpv-x8mh · GitHub severity HIGH
  17. 2026-10-10 06:17 UTCEG score recompute
  18. 2026-10-10 06:17 UTCGHSA enrichmentGHSA-5q52-pjpv-x8mh · GitHub severity HIGH
  19. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  20. 2026-10-09 18:48 UTCGHSA enrichmentGHSA-5q52-pjpv-x8mh · GitHub severity HIGH
  21. 2026-10-09 07:19 UTCGHSA enrichmentGHSA-5q52-pjpv-x8mh · GitHub severity HIGH
  22. 2026-10-08 19:51 UTCEG score recompute
  23. 2026-10-08 19:51 UTCGHSA enrichmentGHSA-5q52-pjpv-x8mh · GitHub severity HIGH
  24. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  25. 2026-10-08 08:18 UTCEG score recompute
  26. 2026-10-08 08:18 UTCGHSA enrichmentGHSA-5q52-pjpv-x8mh · GitHub severity HIGH
  27. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  28. 2026-10-07 20:50 UTCGHSA enrichmentGHSA-5q52-pjpv-x8mh · GitHub severity HIGH
  29. 2026-10-07 09:20 UTCGHSA enrichmentGHSA-5q52-pjpv-x8mh · GitHub severity HIGH
  30. 2026-10-06 21:52 UTCEG score recompute
  31. 2026-10-06 21:52 UTCGHSA enrichmentGHSA-5q52-pjpv-x8mh · GitHub severity HIGH
  32. 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  33. 2026-10-06 10:24 UTCGHSA enrichmentGHSA-5q52-pjpv-x8mh · GitHub severity HIGH
  34. 2026-10-05 22:55 UTCEG score recompute
  35. 2026-10-05 22:55 UTCGHSA enrichmentGHSA-5q52-pjpv-x8mh · GitHub severity HIGH
  36. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  37. 2026-10-05 11:27 UTCGHSA enrichmentGHSA-5q52-pjpv-x8mh · GitHub severity HIGH
  38. 2026-10-05 00:00 UTCEG score recompute
  39. 2026-10-05 00:00 UTCGHSA enrichmentGHSA-5q52-pjpv-x8mh · GitHub severity HIGH
  40. 2026-10-04 23:23 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  41. 2026-10-04 12:32 UTCGHSA enrichmentGHSA-5q52-pjpv-x8mh · GitHub severity HIGH
  42. 2026-10-04 01:04 UTCEG score recompute
  43. 2026-10-04 01:03 UTCGHSA enrichmentGHSA-5q52-pjpv-x8mh · GitHub severity HIGH
  44. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  45. 2026-10-03 13:35 UTCGHSA enrichmentGHSA-5q52-pjpv-x8mh · GitHub severity HIGH
  46. 2026-10-03 02:07 UTCEG score recompute
  47. 2026-10-03 02:07 UTCGHSA enrichmentGHSA-5q52-pjpv-x8mh · GitHub severity HIGH
  48. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  49. 2026-10-02 14:38 UTCGHSA enrichmentGHSA-5q52-pjpv-x8mh · GitHub severity HIGH
  50. 2026-10-02 03:09 UTCEG score recompute
  51. 2026-10-02 03:08 UTCGHSA enrichmentGHSA-5q52-pjpv-x8mh · GitHub severity HIGH
  52. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  53. 2026-10-01 15:39 UTCGHSA enrichmentGHSA-5q52-pjpv-x8mh · GitHub severity HIGH
  54. 2026-10-01 04:11 UTCGHSA enrichmentGHSA-5q52-pjpv-x8mh · GitHub severity HIGH
  55. 2026-09-30 16:43 UTCEG score recompute
  56. 2026-09-30 16:43 UTCGHSA enrichmentGHSA-5q52-pjpv-x8mh · GitHub severity HIGH
  57. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  58. 2026-09-30 14:36 UTCGHSA enrichmentGHSA-5q52-pjpv-x8mh · GitHub severity HIGH
  59. 2026-09-30 02:52 UTCGHSA enrichmentGHSA-5q52-pjpv-x8mh · GitHub severity HIGH
  60. 2026-09-29 15:24 UTCEG score recompute
  61. 2026-09-29 15:24 UTCGHSA enrichmentGHSA-5q52-pjpv-x8mh · GitHub severity HIGH
  62. 2026-09-29 15:09 UTCEG score recompute
  63. 2026-09-29 15:09 UTCGHSA enrichmentGHSA-5q52-pjpv-x8mh · GitHub severity HIGH
  64. 2026-09-29 11:32 UTCEG score recompute
  65. 2026-09-29 10:49 UTCEG score recomputeFirst assessed: 8.8 HIGH
  66. 2026-09-29 10:48 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-95509?
CVE-2026-95509 is a high-severity vulnerability; its CVE record was published on September 29, 2026. Strings optimized for Latin-1 displaying Latin-1 characters cause incorrect String.arg() formatting by an incorrect buffer size calculation, causing out-of-bounds reading.
When was the CVE record for CVE-2026-95509 published?
The CVE record for CVE-2026-95509 was published on September 29, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-95509 actively exploited?
CVE-2026-95509 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (24th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-95509?
CVE-2026-95509 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-95509?
A fix for CVE-2026-95509 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-95509 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-95509?

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