CVE-2025-0007VulnerabilityPublished 24 Nov 2025

CVE-2025-0007: AMD Xilinx Run Time (XRT) · Improper Adherence to Coding Standards

Affects AMD Xilinx Run Time (XRT)Source CVE Database V5

Not known to be exploited · CVSS 5.7 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

5.7Medium

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: Low

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
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: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Nov 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-26.

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

AI-suggested

1. Monitor AMD and Xilinx official channels for patches or updates addressing CVE-2025-0007 and apply them immediately upon release. 2. Restrict local user permissions to the minimum necessary, especially on systems running XRT, to reduce the risk of privilege escalation. 3. Implement strict access controls and audit logging for local user activities to detect suspicious behavior indicative of exploitation attempts. 4. Employ endpoint detection and response (EDR) solutions capable of identifying unusual kernel-level activity or privilege escalation patterns. 5. Conduct regular security reviews and code audits of custom integrations with XRT to ensure adherence to secure coding standards. 6. Isolate critical systems using XRT in segmented network zones to limit lateral movement in case of compromise. 7. Provide security awareness training to users with local access to emphasize the risks of social engineering or inadvertent execution of malicious code. 8. Consider deploying host-based intrusion prevention systems (HIPS) to block unauthorized kernel-level modifications. 9. Maintain up-to-date backups and incident response plans tailored to potential privilege escalation scenarios involving XRT. 10. Collaborate with AMD support for guidance on best practices and vulnerability management related to XRT deployments.

Description

Insufficient validation within Xilinx Run Time framework could allow a local attacker to escalate privileges from user space to kernel space, potentially compromising confidentiality, integrity, and/or availability.

Impact

For European organizations, the impact of CVE-2025-0007 could be significant in sectors relying on AMD Xilinx FPGA acceleration, such as telecommunications, automotive, industrial automation, and research institutions. Successful exploitation could lead to unauthorized kernel-level access, enabling attackers to manipulate system processes, access confidential data, or disrupt availability. This could compromise intellectual property, disrupt critical infrastructure, or lead to data breaches. Given the local access requirement, insider threats or compromised user accounts pose the highest risk. The scope change in the vulnerability means that an exploit could affect multiple system components beyond the initial user context. Organizations using XRT in multi-tenant or shared environments may face increased risk of lateral movement or privilege escalation attacks. The absence of known exploits reduces immediate threat but does not eliminate future risk, especially as attackers develop proof-of-concept code. The medium severity rating suggests that while the vulnerability is not critical, it should be addressed promptly to prevent potential exploitation in sensitive environments.

CWE-710Improper Adherence to Coding Standards (opens in a new tab)
Pillar weakness
The product does not follow certain coding rules for development, which can lead to resultant weaknesses or increase the severity of the associated vulnerabilities.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Policy
Select and require coding standards. Ensure that they include security concerns.
Implementation
Closely follow coding standards, possibly enforcing them upon checkin of the code into a source control system or with periodic analyses.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

amd.com/en/resources/product-security/bulletin/AMD-SB-8014.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 24 Nov 2025, 20:56 UTC

WeaknessesCWE-710

Technical details

References

Community reviews

Related threats