Skip to main content
← Vulnerabilities

Out-of-bounds read vulnerability in CoAP message parsing impacts Qt CoAP

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

6.7MediumCNA
Exploited
No known exploitation
Fix
Fix or patch referenced
Who is exposed
Not reported

Do first: Apply the patch listed under Evidence.

27Pcve.now Index 27 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Data gap: No advisory context yet
  • Reach?/20Reach: unknown (data gap). No tracked technology or package matched
  • Severity6.7/10CVSS 6.7
  • No patch0/5No signal

What would change the score

  • Would score about 72 if added to CISA KEV
  • Would score about 67 if CISA's SSVC rates exploitation active
  • Would score about 32 if advisories confirm default setups are exposed

CVE-2026-103653 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.7 (medium) and affects Qt; a fix or patch is referenced.

Published
Last modified
Published
Not listed in CISA KEV
0.29% · 21st percentile
27/100 · provisional
Fix
Fix or patch referenced
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: yes
  • Technical impact: partial

Summary

The Qt CoAP module, a component of the Qt framework used by applications that communicate over the Constrained Application Protocol, is affected by this flaw. Processing a specially malformed CoAP message can cause an application using it to crash or to keep running while working with incorrect data.

Read the original description

An out-of-bounds read vulnerability in the Qt CoAP message parsing (QCoapInternalReply::createFromFrame()) of the Qt CoAP module. Processing a malformed CoAP message can cause an application using Qt CoAP to crash (loss of availability) or to continue operating on incorrect data (potential loss of integrity).

What to do

  • Apply the patch listed under Evidence.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Affected versions

  • qt Qt

    From 5.13.0 · through 6.8.8; From 6.9.0 · through 6.11.2

Evidence 3

  1. Advisory
  2. Patch
  3. Patch

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-103653

Is CVE-2026-103653 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-103653?

Qt: from 5.13.0 through 6.8.8; from 6.9.0 through 6.11.2.Source: cve.now feed data