tls_verify_call_back() · Integer Signedness Error
Source GCVE Database
Not known to be exploited · CVSS 7.5 High.
Data as of 16 Nov 2026, 01:32 UTC
Thin evidence
One scorer or none| CISA-ADP | CVSS 3.1 | 7.5 |
|---|
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 24 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubobgm/libcoappkg:github/obgm/libcoapOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until a fix is available, avoid processing untrusted TLS certificates or apply any vendor-recommended workarounds if published.
Description
An integer signedness error in the tls_verify_call_back() function of libcoap 4.3.5 can cause a denial of service. This occurs when a crafted TLS certificate triggers i2d_X509() to return -1, which is then incorrectly used as a size parameter for malloc().