CVE-2025-9613VulnerabilityPublished 9 Dec 2025

CVE-2025-9613: PCI Express Integrity and Data Encryption (PCIe IDE) Specification · Incomplete Cleanup

Affects PCI Express Integrity and Data Encryption (PCIe IDE) SpecificationSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 11% 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:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
PCI-SIG PCI Express Integrity and Data Encryption (PCIe IDE) Specification	Affected =0	Fixed in–

AI-suggested

1. Engage with hardware and firmware vendors to obtain patches or updated PCIe IDE specification implementations that address tag reuse and cleanup issues. 2. Conduct a comprehensive inventory of all PCIe-enabled devices within the infrastructure, focusing on those implementing PCIe IDE features. 3. Implement enhanced monitoring of PCIe bus traffic to detect anomalies indicative of tag aliasing or misrouted completions, using specialized hardware or software tools where available. 4. Apply strict access controls to PCIe interfaces, limiting physical and logical access to trusted personnel and systems to reduce the risk of malicious PCIe traffic injection. 5. Where possible, isolate critical PCIe devices in segmented environments to contain potential exploitation impact. 6. Collaborate with PCI-SIG and industry groups for guidance on best practices and updates related to PCIe IDE security. 7. Review and update incident response plans to include scenarios involving PCIe communication compromise. 8. Educate system architects and security teams on the implications of PCIe vulnerabilities to ensure informed risk management decisions.

Description

A vulnerability was discovered in the PCI Express (PCIe) Integrity and Data Encryption (IDE) specification, where insufficient guidance on tag reuse after completion timeouts may allow multiple outstanding Non-Posted Requests to share the same tag. This tag aliasing condition can result in completions being delivered to the wrong security context, potentially compromising data integrity and confidentiality.

Impact

For European organizations, the vulnerability poses a risk to data confidentiality and integrity within systems using PCIe IDE-enabled devices. This includes servers, storage arrays, and network interface cards common in enterprise data centers and cloud infrastructure. Compromise of PCIe communications could lead to unauthorized data exposure or data corruption, impacting sensitive business information and critical operations. Industries such as finance, healthcare, telecommunications, and government services are particularly at risk due to their reliance on secure, high-performance computing infrastructure. The vulnerability could also undermine trust in hardware security features, complicating compliance with European data protection regulations like GDPR. Although availability is not directly impacted, the potential for data breaches and integrity failures could cause operational disruptions and reputational damage. The lack of known exploits currently provides a window for proactive mitigation, but the complexity of PCIe environments may delay patch deployment. Organizations with large-scale deployments of PCIe devices must prioritize risk assessment and remediation to prevent exploitation.

CWE-459Incomplete Cleanup (opens in a new tab)
Base weakness
The product does not properly "clean up" and remove temporary or supporting resources after they have been used.
Architecture and Design · Implementation
Temporary files and other supporting resources should be deleted/released immediately after they are no longer needed.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Dec 2025, 21:02 UTC

WeaknessesCWE-459

Technical details

References

Community reviews

Related threats