CVE-2025-52539VulnerabilityPublished 24 Nov 2025

CVE-2025-52539: AMD Xilinx Run Time (XRT) · Stack-based Buffer Overflow

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

Not known to be exploited · CVSS 7.3 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.3High

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

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H

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

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: 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: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

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-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

AI-suggested

1. Monitor AMD and Xilinx official channels closely for patches or updates addressing CVE-2025-52539 and apply them promptly once available. 2. Restrict local access to systems running XRT to trusted personnel only, employing strict access controls and user authentication mechanisms. 3. Implement host-based intrusion detection systems (HIDS) to monitor for anomalous behavior or attempts to exploit buffer overflows in XRT processes. 4. Conduct regular security audits and code reviews of custom FPGA-related software integrations to detect potential misuse of the AXI interface. 5. Use virtualization or containerization to isolate XRT environments where feasible, limiting the blast radius of any exploit. 6. Educate internal teams about the risks of local privilege escalation and buffer overflow attacks to reduce insider threat vectors. 7. Employ memory protection mechanisms such as stack canaries and address space layout randomization (ASLR) on affected systems to mitigate exploitation success.

Description

CVE-2025-52539 is a high-severity stack-based buffer overflow vulnerability in AMD's Xilinx Run Time (XRT) environment. It allows a local attacker to read or corrupt data via the advanced extensible interface (AXI), potentially impacting confidentiality, integrity, and availability. The vulnerability requires local access but no privileges or user interaction. Exploitation could lead to data leakage or system disruption. No known exploits are currently reported in the wild. European organizations using XRT in FPGA or hardware acceleration deployments are at risk. Mitigation involves applying vendor patches once available and restricting local access to trusted users. Countries with significant industrial, telecommunications, and research sectors using Xilinx products are more likely to be affected. The CVSS score is 7.3, indicating a high severity threat.

Impact

For European organizations, the impact of CVE-2025-52539 can be significant, especially in sectors that rely heavily on FPGA technology such as telecommunications, automotive, aerospace, industrial automation, and research institutions. Confidentiality breaches could expose proprietary algorithms or sensitive operational data. Integrity compromises might lead to corrupted data processing or erroneous outputs in critical systems, potentially causing operational failures or safety risks. Availability impacts could disrupt services dependent on FPGA acceleration, leading to downtime and financial losses. Since exploitation requires local access, insider threats or compromised internal systems pose the greatest risk. The lack of current public exploits reduces immediate threat but does not eliminate future risks. Organizations with Xilinx hardware deployments in Europe must consider this vulnerability in their risk assessments and incident response planning.

Summary

CVE-2025-52539 is a stack-based buffer overflow vulnerability identified in the AMD Xilinx Run Time (XRT) environment, which is used to manage and interface with Xilinx FPGA devices. The vulnerability arises from improper handling of data buffers related to the advanced extensible interface (AXI), a critical communication protocol used within FPGA architectures for data transfer. A local attacker, without requiring privileges or user interaction, can exploit this flaw to read or corrupt sensitive data passing through the AXI interface. This can lead to breaches in confidentiality by exposing sensitive data, integrity violations by corrupting data, or availability issues by causing system crashes or unpredictable behavior. The vulnerability is classified under CWE-121, indicating a classic stack-based buffer overflow, which is a well-known and dangerous class of memory corruption bugs. The CVSS 3.1 score of 7.3 reflects the high impact and relatively low complexity of exploitation, although it requires local access. No patches or exploits are currently publicly available, but the vulnerability is officially published and reserved by AMD. Given the role of XRT in FPGA management, exploitation could affect critical systems relying on hardware acceleration or programmable logic devices.

CWE-121Stack-based Buffer Overflow (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #14
A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
Architecture and Design
Use an abstraction library to abstract away risky APIs. Not a complete solution.
Implementation
Implement and perform bounds checking on input.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
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 1 Dec 2025, 20:41 UTC

WeaknessesCWE-121

Technical details

References

Community reviews

Related threats