Is there a public exploit for CVE-2026-0101?

Yes. Proof-of-concept code for CVE-2026-0101 has been published publicly.

Is there a proof of concept for CVE-2026-0101?

Yes — 1 proof-of-concept entry is linked on this page, from public repositories and community submissions. They are listed for authorised testing only.

How severe is CVE-2026-0101?

CVE-2026-0101 scores CVSS 6.8 (v4.0), rated medium.

What does CVE-2026-0101 affect?

CVE-2026-0101 affects AMD AMD EPYC™ Embedded 9005 Series Processors, AMD EPYC™ 9005 Series Processors.

6.8 Medium

Improper validation of specified quantities in input within AMD Power Management Firmware (PMFW) could allow a local attacker to pass…

CVE-2026-0101

Improper validation of specified quantities in input within AMD Power Management Firmware (PMFW) could allow a local attacker to pass unsanitized input, potentially resulting in a system crash or denial of service.

Proof-of-concept code is published

Public PoC

Public PoCGeorge0Papasotiriou/CVE-2026-0101-BLE-Address-Spoofing-via-Weak-Resolvable-Private-Address

Signals come from Exploit-DB, Metasploit, Nuclei and published proof-of-concept repositories. Their absence means nothing was found, not that nothing exists.

Assessment

CVSS: 6.8 (v4.0)
Severity: Medium
Known exploited: Not listed in CISA KEV
Exploit availability: Public PoC
Published: 12 November 2026
Last updated: 12 November 2026
Affected: AMD · AMD EPYC™ 9005 Series Processors · AMD EPYC™ Embedded 9005 Series Processors
Assigner: AMD

CVSS vectorCVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

At the source

EUVD (ENISA)

References

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

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept

Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.

Title *

Proof of concept *

Write-up (optional)

Affected versions (optional)

Name or handle (optional)

References (optional, one URL per line)

Licence for your contribution *

Private contact (optional, never shown)

Before you submit * This vulnerability is already publicly disclosed (it has a published CVE). This material comes only from testing I was authorised to perform. I have the legal right to publish this content and am not breaching any agreement by doing so. It contains no live credentials, personal data, or anything targeting systems I am not authorised to test. I understand it will be reviewed before it appears publicly and may be rejected. I agree to the submission terms.

What is 9 + 2? *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-0101