cve.bz

CVE-2026-40275 blackberry ltd: Heap-based Buffer Overflow

8.4 highEPSS 0.1%

High (8.4) in blackberry ltd. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
Heap-based Buffer Overflow in the DCMD_PROC_EVENT handler of the procnto could allow an attacker with local access to cause an information disclosure, data tampering or a crash of the QNX Neutrino kernel.

Severity

CVSS 3.1

8.4 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.1% estimated probability of exploitation activity in the next 30 days; 2nd percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-122 Heap-based Buffer Overflow
Published
Modified
Assigned by
blackberry (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-40275 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-40275?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-40275?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-40275 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-40275

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-40275](https://cve.bz/cve/badge/CVE-2026-40275.svg)](https://cve.bz/cve/CVE-2026-40275)

HTML:

<a href="https://cve.bz/cve/CVE-2026-40275"><img src="https://cve.bz/cve/badge/CVE-2026-40275.svg" alt="CVE-2026-40275"></a>

Affected

  • blackberry ltd:qnx os for medical
  • blackberry ltd:qnx os for safety
  • blackberry ltd:qnx software development platform

Versions

From the CNA's record in the CVE List.

ProductAffected
BlackBerry Ltd QNX Software Development Platformcpe:2.3:a:blackberry:qnx_software_development_platform:7.1:*:*:*
BlackBerry Ltd QNX Software Development Platformcpe:2.3:a:blackberry:qnx_software_development_platform:7.0:*:*:*
BlackBerry Ltd QNX OS for Safetycpe:2.3:o:blackberry:qnx_os_for_safety:2.2:9:*:*:*:*:*:*
BlackBerry Ltd QNX OS for Safetycpe:2.3:o:blackberry:qnx_os_for_safety:2.1:6:*:*:*:*:*:*
BlackBerry Ltd QNX OS for Safetycpe:2.3:o:blackberry:qnx_os_for_safety:2.0:4:*:*:*:*:*:*
BlackBerry Ltd QNX OS for Medicalcpe:2.3:o:blackberry:qnx_os_for_medical:2.0:3:*:*:*:*:*:*

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON