Skip to main content
CVE-2025-2474VulnerabilityPublished

CVE-2025-2474: BlackBerry QNX Software Development Platform (SDP) · Out-of-bounds Write

Affects BlackBerry QNX Software Development Platform (SDP)Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
BlackBerry QNX Software Development Platform (SDP)Affected
  • =8.0
  • =7.1
  • =7.0
Fixed in–

AI-suggested

Immediate mitigation steps include: 1) Inventory and identify all devices and systems running affected versions (7.0, 7.1, 8.0) of BlackBerry QNX SDP within the organization. 2) Apply vendor patches as soon as they become available; monitor BlackBerry security advisories closely. 3) Implement network-level protections such as strict firewall rules and segmentation to limit exposure of vulnerable devices to untrusted networks, especially restricting access to services that process PCX images. 4) Employ intrusion detection and prevention systems (IDS/IPS) with updated signatures to detect anomalous PCX image processing or exploitation attempts. 5) Where patching is delayed, consider disabling or restricting the use of the PCX image codec if feasible, or sanitize inputs to prevent processing of untrusted PCX files. 6) Conduct thorough security assessments and penetration testing focusing on embedded systems and QNX-based devices to identify potential exploitation paths. 7) Enhance monitoring and logging around affected systems to detect early signs of exploitation or abnormal behavior. 8) Educate relevant operational technology (OT) and IT staff about the vulnerability and response procedures. These targeted actions go beyond generic advice by focusing on embedded systems management, network segmentation, and proactive detection tailored to the QNX environment.

Description

Out-of-bounds write in the PCX image codec in QNX SDP versions 8.0, 7.1 and 7.0 could allow an unauthenticated attacker to cause a denial-of-service condition or execute code in the context of the process using the image codec.

References

Community reviews

Loading reviews…