Skip to content
Hardware

CVE-2025-52533

8.7
High
EPSS 0.28%Feb 13, 2026

On-chip debug interface access control flaw allows privileged activation of debug mode.

common questions

Is CVE-2025-52533 being exploited?

Not confirmed. CVE-2025-52533 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.28% probability of exploitation in the next 30 days.

How severe is CVE-2025-52533?

CVE-2025-52533 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-52533?

Not known from our data. No patch reference has been recorded for CVE-2025-52533, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What should I do about CVE-2025-52533?

Restrict/disable unused debug interfaces; monitor physical access; patch when available.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
impact

Privileged attacker can enable debug interface to read/modify memory, risking data confidentiality and integrity.

action required

Monitor only

affected versions
AMD AMD EPYC™ 7001 Series Processors
  • affectedNo Fix Planned
AMD AMD EPYC™ 7002 Series Processors
  • affectedNo Fix Planned
AMD AMD EPYC™ Embedded 3000 Series Processors
  • affectedNo fix planned
AMD AMD EPYC™ Embedded 7002 Series Processors
  • affectedNo fix planned

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free