CVE-2025-61081

✕ Withdrawn — historical dataHIGHNVD 7.5Elevated
7.5CVSS
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

In BYD Atto3, an attacker can obtain an authentication key through Brute Force attack, which is permanently available. The authentication key enables flash to the Electronic Parking Break (EPB) and Supplemental Restoration System (SRS) related ECUs.

CVSS v3
7.5
EchelonGraph score
Not yet assessedThis CVE record was withdrawn by its numbering authority, so there is no vulnerability to rate.
EG Score
—
EG Risk
—
EPSS PROB
<0.1%
EPSS %ILE
8th
KEV
Not listed

Published

May 19, 2026

Last Modified

May 19, 2026

Advisory Details (2)

Auto-updated May 19, 2026
No fix on record yet.
generic

Notion

https://www.notion.so/CVE-2025-61081-26215fb6156c8000b338db3c2011f637
generic

Notion

https://www.notion.so/BYD-Atto3-26215fb6156c8000b338db3c2011f637?source=copy_link

Vendor Advisories for CVE-2025-61081(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 0× in last 7d / 0× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-24 00:19 UTCGHSA enrichment
  2. 2026-08-20 19:01 UTCGHSA enrichment
  3. 2026-08-16 03:34 UTCGHSA enrichment
  4. 2026-08-12 12:00 UTCGHSA enrichment
  5. 2026-08-09 01:48 UTCGHSA enrichment
  6. 2026-08-05 21:20 UTCGHSA enrichment
  7. 2026-08-01 17:53 UTCEG score recompute
  8. 2026-08-01 17:53 UTCGHSA enrichment
  9. 2026-07-23 03:00 UTCEG score recompute▼ 7.50
  10. 2026-06-29 20:42 UTCGHSA enrichment
  11. 2026-06-28 07:57 UTCGHSA enrichment
  12. 2026-06-27 20:24 UTCGHSA enrichment
  13. 2026-06-27 07:35 UTCGHSA enrichment
  14. 2026-06-26 19:46 UTCGHSA enrichment
  15. 2026-06-26 03:52 UTCGHSA enrichment
  16. 2026-06-25 16:50 UTCGHSA enrichment
  17. 2026-06-17 22:44 UTCGHSA enrichment
  18. 2026-06-17 11:42 UTCGHSA enrichment
  19. 2026-06-16 20:47 UTCGHSA enrichment
  20. 2026-06-16 03:04 UTCGHSA enrichment
  21. 2026-06-15 16:00 UTCGHSA enrichment
  22. 2026-06-14 23:50 UTCGHSA enrichment
  23. 2026-06-14 12:47 UTCGHSA enrichment
  24. 2026-06-14 01:45 UTCGHSA enrichment
  25. 2026-06-13 14:33 UTCGHSA enrichment
Show 57 more
  1. 2026-06-13 01:57 UTCGHSA enrichment
  2. 2026-06-12 14:55 UTCGHSA enrichment
  3. 2026-06-12 03:54 UTCGHSA enrichment
  4. 2026-06-11 16:53 UTCGHSA enrichment
  5. 2026-06-11 05:51 UTCGHSA enrichment
  6. 2026-06-10 18:50 UTCGHSA enrichment
  7. 2026-06-10 07:49 UTCGHSA enrichment
  8. 2026-06-09 20:44 UTCGHSA enrichment
  9. 2026-06-09 09:36 UTCGHSA enrichment
  10. 2026-06-08 22:35 UTCGHSA enrichment
  11. 2026-06-08 11:33 UTCGHSA enrichment
  12. 2026-06-08 00:32 UTCGHSA enrichment
  13. 2026-06-07 13:31 UTCGHSA enrichment
  14. 2026-06-07 02:29 UTCGHSA enrichment
  15. 2026-06-06 15:27 UTCGHSA enrichment
  16. 2026-06-06 04:26 UTCGHSA enrichment
  17. 2026-06-05 17:25 UTCGHSA enrichment
  18. 2026-06-05 06:24 UTCGHSA enrichment
  19. 2026-06-04 19:23 UTCGHSA enrichment
  20. 2026-06-04 08:22 UTCGHSA enrichment
  21. 2026-06-03 21:21 UTCGHSA enrichment
  22. 2026-06-03 10:19 UTCGHSA enrichment
  23. 2026-06-02 23:17 UTCGHSA enrichment
  24. 2026-06-02 12:15 UTCGHSA enrichment
  25. 2026-06-02 01:14 UTCGHSA enrichment
  26. 2026-06-01 14:12 UTCGHSA enrichment
  27. 2026-06-01 13:51 UTCEPSS rescore
  28. 2026-06-01 13:51 UTCEPSS rescore
  29. 2026-06-01 03:10 UTCGHSA enrichment
  30. 2026-05-31 22:30 UTCEPSS rescore
  31. 2026-05-31 22:30 UTCEPSS rescore
  32. 2026-05-31 00:16 UTCEPSS rescore
  33. 2026-05-31 00:16 UTCEPSS rescore
  34. 2026-05-29 13:44 UTCEPSS rescore
  35. 2026-05-28 13:44 UTCEPSS rescore
  36. 2026-05-28 13:44 UTCEPSS rescore
  37. 2026-05-28 13:44 UTCEPSS rescore
  38. 2026-05-27 13:40 UTCEPSS rescore
  39. 2026-05-27 13:40 UTCEPSS rescore
  40. 2026-05-27 13:40 UTCEPSS rescore
  41. 2026-05-27 13:40 UTCEPSS rescore
  42. 2026-05-26 13:44 UTCEPSS rescore
  43. 2026-05-26 13:44 UTCEPSS rescore
  44. 2026-05-26 13:43 UTCEPSS rescore
  45. 2026-05-26 07:18 UTCEPSS rescore
  46. 2026-05-26 07:18 UTCEPSS rescore
  47. 2026-05-26 07:18 UTCEPSS rescore
  48. 2026-05-23 15:21 UTCEPSS rescore
  49. 2026-05-22 21:16 UTCEPSS rescore
  50. 2026-05-22 21:16 UTCEPSS rescore
  51. 2026-05-21 22:43 UTCEPSS rescore
  52. 2026-05-20 22:37 UTCEPSS rescore
  53. 2026-05-20 22:37 UTCEPSS rescore
  54. 2026-05-20 22:37 UTCEPSS rescore
  55. 2026-05-20 22:37 UTCEPSS rescore
  56. 2026-05-20 11:40 UTCEG score recompute
  57. 2026-05-20 11:40 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-61081?
CVE-2025-61081 is a high vulnerability published on May 19, 2026. In BYD Atto3, an attacker can obtain an authentication key through Brute Force attack, which is permanently available. The authentication key enables flash to the Electronic Parking Break (EPB) and Supplemental Restoration System (SRS) related ECUs.
When was CVE-2025-61081 disclosed?
CVE-2025-61081 was first published on May 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-61081 actively exploited?
CVE-2025-61081 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-61081?
CVE-2025-61081 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2025-61081?
No fix for CVE-2025-61081 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2025-61081 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-61081

Explore →

Is Your Infrastructure Affected by CVE-2025-61081?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs