CVE-2025-52471

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.7%, top 49% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

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

ESF-IDF is the Espressif Internet of Things (IOT) Development Framework. An integer underflow vulnerability has been identified in the ESP-NOW protocol implementation within the ESP Wi-Fi component of versions 5.4.1, 5.3.3, 5.2.5, and 5.1.6 of the ESP-IDF framework. This issue stems from insufficient validation of user-supplied data length in the packet receive function. Under certain conditions, this may lead to out-of-bounds memory access and may allow arbitrary memory write operations. On systems without a memory protection scheme, this behavior could potentially be used to achieve remote code execution (RCE) on the target device. In versions 5.4.2, 5.3.4, 5.2.6, and 5.1.6, ESP-NOW has added more comprehensive validation logic on user-supplied data length during packet reception to prevent integer underflow caused by negative value calculations. For ESP-IDF v5.3 and earlier, a workaround can be applied by validating that the data_len parameter received in the RX callback (registered via esp_now_register_recv_cb()) is a positive value before further processing. For ESP-IDF v5.4 and later, no application-level workaround is available. Users are advised to upgrade to a patched version of ESP-IDF to take advantage of the built-in mitigation.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
59(Track)
EG Risk 59/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
57%
KEV
Not listed

Published

June 24, 2025

Last Modified

January 22, 2026

Advisory Details (7)

Auto-updated Sep 17, 2026
Patch available. Sources: github_commit, github.
github Patch Available

ESP-NOW Integer Underflow Vulnerability Advisory · Advisory · espressif/esp-idf · GitHub

https://github.com/espressif/esp-idf/security/advisories/GHSA-hqhh-cp47-fv5g
github_commit

commit edc227c5eaec (espressif/esp-idf)

Fix landed in espressif/esp-idf commit edc227c5eaec — awaiting tagged release

https://github.com/espressif/esp-idf/commit/edc227c5eaeced999b5212943a9434379f8aad80
github_commit

commit df7757d82798 (espressif/esp-idf)

Fix landed in espressif/esp-idf commit df7757d82798 — awaiting tagged release

https://github.com/espressif/esp-idf/commit/df7757d8279871fa7a2f42ef3962c6c1ec88b8a2
github_commit

commit d6ec5a52255b (espressif/esp-idf)

Fix landed in espressif/esp-idf commit d6ec5a52255b — awaiting tagged release

https://github.com/espressif/esp-idf/commit/d6ec5a52255b17c1d6ef379e89f9de2c379042f8
github_commit

commit d4dafbdc3572 (espressif/esp-idf)

Fix landed in espressif/esp-idf commit d4dafbdc3572 — awaiting tagged release

https://github.com/espressif/esp-idf/commit/d4dafbdc3572387cd4f9a62b776580bc4ac3bde7
github_commit

commit c5fc81917805 (espressif/esp-idf)

Fix landed in espressif/esp-idf commit c5fc81917805 — awaiting tagged release

https://github.com/espressif/esp-idf/commit/c5fc81917805f99e687c81cc56b68dc5df7ef8b5
github_commit

commit b1a379d57430 (espressif/esp-idf)

Fix landed in espressif/esp-idf commit b1a379d57430 — awaiting tagged release

https://github.com/espressif/esp-idf/commit/b1a379d57430d265a53aca13d59ddfbf2e7ac409

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 32× 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.

Showing the most recent 100 of 153 total refreshes for this CVE.

  1. 2026-09-19 15:42 UTCEPSS rescore
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-18 19:27 UTCEPSS rescore
  4. 2026-09-17 19:29 UTCEPSS rescore
  5. 2026-09-16 14:07 UTCEPSS rescore
  6. 2026-09-16 05:14 UTCEPSS rescore
  7. 2026-09-13 16:46 UTCEPSS rescore
  8. 2026-09-13 08:24 UTCOSV refresh
  9. 2026-09-12 15:00 UTCEPSS rescore
  10. 2026-09-11 14:52 UTCEPSS rescore
  11. 2026-09-11 09:36 UTCEPSS rescore
  12. 2026-09-10 09:34 UTCEPSS rescore
  13. 2026-09-08 21:59 UTCEPSS rescore
  14. 2026-09-07 16:00 UTCEPSS rescore
  15. 2026-09-06 13:47 UTCEPSS rescore
  16. 2026-09-05 15:28 UTCEPSS rescore
  17. 2026-09-04 05:06 UTCEPSS rescore
  18. 2026-09-02 14:11 UTCEPSS rescore
  19. 2026-09-01 13:53 UTCEPSS rescore
  20. 2026-09-01 04:38 UTCEPSS rescore
  21. 2026-08-30 19:16 UTCEPSS rescore
  22. 2026-08-30 01:21 UTCEPSS rescore
  23. 2026-08-28 21:40 UTCEPSS rescore
  24. 2026-08-27 14:24 UTCEPSS rescore
  25. 2026-08-26 14:45 UTCEPSS rescore
Show 75 more
  1. 2026-08-25 13:48 UTCEPSS rescore
  2. 2026-08-25 09:41 UTCOSV refresh
  3. 2026-08-24 14:16 UTCEPSS rescore
  4. 2026-08-24 09:22 UTCEPSS rescore
  5. 2026-08-23 00:18 UTCEPSS rescore
  6. 2026-08-21 23:48 UTCEPSS rescore
  7. 2026-08-20 22:54 UTCEPSS rescore
  8. 2026-08-19 17:03 UTCEPSS rescore
  9. 2026-08-18 13:47 UTCEPSS rescore
  10. 2026-08-17 13:46 UTCEPSS rescore
  11. 2026-08-16 14:55 UTCEPSS rescore
  12. 2026-08-16 02:13 UTCEPSS rescore
  13. 2026-08-15 01:29 UTCEPSS rescore
  14. 2026-08-13 21:59 UTCEPSS rescore
  15. 2026-08-12 13:50 UTCEPSS rescore
  16. 2026-08-12 13:50 UTCEPSS rescore
  17. 2026-08-11 13:42 UTCEPSS rescore
  18. 2026-08-10 23:59 UTCEPSS rescore
  19. 2026-08-09 13:46 UTCEPSS rescore
  20. 2026-08-09 02:22 UTCOSV refresh
  21. 2026-08-08 16:36 UTCEPSS rescore
  22. 2026-08-07 16:26 UTCEPSS rescore
  23. 2026-08-06 13:46 UTCEPSS rescore
  24. 2026-08-05 19:16 UTCEPSS rescore
  25. 2026-08-04 15:09 UTCEPSS rescore
  26. 2026-08-04 15:09 UTCEPSS rescore
  27. 2026-08-04 10:37 UTCEPSS rescore
  28. 2026-08-03 10:35 UTCEPSS rescore
  29. 2026-08-02 02:26 UTCEPSS rescore
  30. 2026-08-01 04:15 UTCEPSS rescore
  31. 2026-07-30 16:27 UTCEPSS rescore
  32. 2026-07-30 01:30 UTCEPSS rescore
  33. 2026-07-28 15:35 UTCEPSS rescore
  34. 2026-07-26 14:54 UTCEPSS rescore
  35. 2026-07-25 14:17 UTCEPSS rescore
  36. 2026-07-24 14:17 UTCEPSS rescore
  37. 2026-07-24 02:11 UTCOSV refresh
  38. 2026-07-23 14:18 UTCEPSS rescore
  39. 2026-07-23 02:58 UTCEG score recompute
  40. 2026-07-22 14:08 UTCEPSS rescore
  41. 2026-07-22 14:07 UTCEPSS rescore
  42. 2026-07-21 15:24 UTCEPSS rescore
  43. 2026-07-20 17:08 UTCEPSS rescore
  44. 2026-07-19 14:30 UTCEPSS rescore
  45. 2026-07-19 14:30 UTCEPSS rescore
  46. 2026-07-19 02:28 UTCEPSS rescore
  47. 2026-07-18 10:04 UTCEPSS rescore
  48. 2026-07-16 17:02 UTCEPSS rescore
  49. 2026-07-15 16:57 UTCEPSS rescore
  50. 2026-07-15 16:57 UTCEPSS rescore
  51. 2026-07-15 01:59 UTCEPSS rescore
  52. 2026-07-15 01:59 UTCEPSS rescore
  53. 2026-07-13 22:29 UTCEPSS rescore
  54. 2026-07-13 06:12 UTCEPSS rescore
  55. 2026-07-13 06:12 UTCEPSS rescore
  56. 2026-07-12 05:46 UTCEPSS rescore
  57. 2026-07-11 08:27 UTCEPSS rescore
  58. 2026-07-11 08:27 UTCEPSS rescore
  59. 2026-07-09 19:09 UTCEPSS rescore
  60. 2026-07-08 15:15 UTCEPSS rescore
  61. 2026-07-07 13:45 UTCEPSS rescore
  62. 2026-07-06 21:04 UTCOSV refresh
  63. 2026-07-06 16:27 UTCEPSS rescore
  64. 2026-07-06 16:27 UTCEPSS rescore
  65. 2026-07-06 02:23 UTCEPSS rescore
  66. 2026-07-06 02:23 UTCEPSS rescore
  67. 2026-07-05 02:30 UTCEPSS rescore
  68. 2026-07-04 06:30 UTCEPSS rescore
  69. 2026-07-02 17:01 UTCEPSS rescore
  70. 2026-07-01 15:06 UTCEPSS rescore
  71. 2026-06-30 23:22 UTCEPSS rescore
  72. 2026-06-29 14:06 UTCEPSS rescore
  73. 2026-06-29 14:06 UTCEPSS rescore
  74. 2026-06-28 14:07 UTCEPSS rescore
  75. 2026-06-28 14:07 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-52471?
CVE-2025-52471 is a critical vulnerability published on June 24, 2025. ESF-IDF is the Espressif Internet of Things (IOT) Development Framework. An integer underflow vulnerability has been identified in the ESP-NOW protocol implementation within the ESP Wi-Fi component of versions 5.4.1, 5.3.3, 5.2.5, and 5.1.6 of the ESP-IDF framework. This issue stems from…
When was CVE-2025-52471 disclosed?
CVE-2025-52471 was first published in the National Vulnerability Database on June 24, 2025, with the most recent update on January 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-52471 actively exploited?
CVE-2025-52471 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 43.4% of all scored CVEs.
What is the CVSS score of CVE-2025-52471?
CVE-2025-52471 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2025-52471?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-52471, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-52471?

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