CVE-2025-54070

MEDIUMNVD 6.96.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 6.9 under NVD CVSS v3. EPSS exploit probability: 0.4% (34th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2025-21789 (ENISA EUVD) · GHSA-9rcw-c2f9-2j55 (GitHub Security Advisories)Source: ENISA EUVD

6.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

OpenZeppelin Contracts is a library for secure smart contract development. Starting in version 5.2.0 and prior to version 5.4.0, the lastIndexOf(bytes,byte,uint256) function of the Bytes.sol library may access uninitialized memory when the following two conditions hold: 1) the provided buffer length is empty (i.e. buffer.length == 0) and position is not 2**256 - 1 (i.e. pos != type(uint256).max). The pos argument could be used to access arbitrary data outside of the buffer bounds. This could lead to the operation running out of gas, or returning an invalid index (outside of the empty buffer). Processing this invalid result for accessing the buffer would cause a revert under normal conditions. When triggered, the function reads memory at offset buffer + 0x20 + pos. If memory at that location (outside the buffer) matches the search pattern, the function would return an out of bound index instead of the expected type(uint256).max. This creates unexpected behavior where callers receive a valid-looking index pointing outside buffer bounds. Subsequent memory accesses that don't check bounds and use the returned index must carefully review the potential impact depending on their setup. Code relying on this function returning type(uint256).max for empty buffers or using the returned index without bounds checking could exhibit undefined behavior. Users should upgrade to version 5.4.0 to receive a patch.

CVSS v3
6.9
EG Score
6.9MEDIUMmedium confidence
EG Risk
31
EG Risk 31/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity69% × 45%
Impact severity (EG Severity): CVSS 6.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
34th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.9): severity, escalated by confirmed exploitation. This CVE's 6.9 is its impact severity (EG Severity), not escalated.

EG Severity
6.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 17, 2025

Last Modified

April 15, 2026

Advisory Details (2)

Auto-updated Oct 23, 2026
Patch available. Sources: github_release, github.
GitHub advisoryMentions a patch (unverified)

Bytes's lastIndexOf function with position argument performs out-of-bound memory access on empty buffers · Advisory · OpenZeppelin/openzeppelin-contracts · GitHub

https://github.com/OpenZeppelin/openzeppelin-contracts/security/advisories/GHSA-9rcw-c2f9-2j55
GitHub release Patch Available

v5.4.0

Patch available: OpenZeppelin/openzeppelin-contracts v5.4.0

https://github.com/OpenZeppelin/openzeppelin-contracts/releases/tag/v5.4.0

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npm@openzeppelin/contracts @ 5.4.0 (fixes >= 5.2.0, < 5.4.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 1 ecosystem)
npm(2)
PackageVulnerable rangeFix by version rangeDependents
@openzeppelin/contracts—
  • 5.2.0 up to 5.4.0: fixed in 5.4.0
—
@openzeppelin/contracts-upgradeable—
  • 5.2.0 up to 5.4.0: fixed in 5.4.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 230 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 135 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2025-54070?
CVE-2025-54070 is a medium-severity vulnerability; its CVE record was published on July 17, 2025. OpenZeppelin Contracts is a library for secure smart contract development. Starting in version 5.2.0 and prior to version 5.4.0, the lastIndexOf(bytes,byte,uint256) function of the Bytes.sol library may access uninitialized memory when the following two conditions hold: 1) the provided buffer…
When was the CVE record for CVE-2025-54070 published?
The CVE record for CVE-2025-54070 was published on July 17, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 15, 2026; the record at its source may have been updated since.
Is CVE-2025-54070 actively exploited?
CVE-2025-54070 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-54070?
CVE-2025-54070 has a CVSS v3 base score of 6.9 (NVD).
How do I remediate CVE-2025-54070?
A fix for CVE-2025-54070 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-54070

Explore →

Is Your Infrastructure Affected by CVE-2025-54070?

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

Book a Demo →Browse All CVEs