How severe is CVE-2025-52539?

CVE-2025-52539 has a CVSS 3.x base score of 7.3, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability high.

Is CVE-2025-52539 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (2nd percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2025-52539?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2025-52539 have an EU (EUVD) identifier?

Yes. CVE-2025-52539 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-198987.

When was CVE-2025-52539 published?

CVE-2025-52539 was published on 2025-11-24 and last updated on 2026-06-17.

CVE-2025-52539

CVE-2025-52539 is a high-severity vulnerability with a CVSS 3.x base score of 7.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-121.

Key facts

Severity: High (CVSS 3.x base score 7.3)
EPSS exploit prediction: 0% (2nd percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-198987
Weakness: CWE-121
Published: 2025-11-24
Last modified: 2026-06-17

Description

A buffer overflow with Xilinx Run Time Environment may allow a local attacker to read or corrupt data from the advanced extensible interface (AXI), potentially resulting in loss of confidentiality, integrity, and/or availability.

Frequently asked questions

What is CVE-2025-52539?: A buffer overflow with Xilinx Run Time Environment may allow a local attacker to read or corrupt data from the advanced extensible interface (AXI), potentially resulting in loss of confidentiality, integrity, and/or availability.
How severe is CVE-2025-52539?: CVE-2025-52539 has a CVSS 3.x base score of 7.3, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability high.
Is CVE-2025-52539 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (2nd percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-52539?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-52539 have an EU (EUVD) identifier?: Yes. CVE-2025-52539 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-198987.
When was CVE-2025-52539 published?: CVE-2025-52539 was published on 2025-11-24 and last updated on 2026-06-17.

References

https://www.amd.com/en/resources/product-security/bulletin/AMD-SB-8014.html

Other CWE-121 (Stack-based Buffer Overflow) vulnerabilities

CVE-2026-12848 — Critical (CVSS 10.0): GV-I/O Box 4E is a smart embedded device with 4 input and 4 relays output that can be controlled over Ethernet and…
CVE-2026-12847 — Critical (CVSS 10.0): GV-I/O Box 4E is a smart embedded device with 4 input and 4 relays output that can be controlled over Ethernet and…
CVE-2026-12846 — Critical (CVSS 10.0): GV-I/O Box 4E is a smart embedded device with 4 input and 4 relays output that can be controlled over Ethernet and…
CVE-2026-12485 — Critical (CVSS 10.0): GV-I/O Box 4E is a smart embedded device with 4 input and 4 relays output that can be controlled over Ethernet and…
CVE-2026-37541 — Critical (CVSS 10.0): Buffer overflow vulnerability in Open Vehicle Monitoring System 3 (OVMS3) 3.3.005. In canformat_gvret.cpp, the length…
CVE-2026-42996 — Critical (CVSS 10.0): JS8Call through 2.3.1 and JS8Call-improved before 3.0 have a stack-based buffer overflow via a radio transmission of…

Browse all CWE-121 (Stack-based Buffer Overflow) vulnerabilities →