CVE-2026-45325

HIGHPre-NVD 8.28.2
EchelonGraph scoreLOW confidence

This high-severity CVE scores 8.2 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 82% 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: cna:github_m, epss
8.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.2Exploit: NoneExposed: 0

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

@tmlmobilidade/utils has prototype pollution in its setValueAtPath

Impact

Prototype pollution vulnerability in @tmlmobilidade/utils for setValueAtPath().

Patches

A fix is available in versions 20260509.0340.15 and up.

CVSS v3
8.2
EG Score
8.2(low)
EPSS
17.8%
KEV
Not listed

Published

May 18, 2026

Last Modified

May 18, 2026

Vendor Advisories for CVE-2026-45325(1)

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

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
@tmlmobilidade/utils—20260509.0340.15—

Data Freshness Timeline

(refreshed 0× in last 7d / 19× 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-06-29 21:09 UTCEG score recompute
  2. 2026-06-28 09:39 UTCEG score recompute
  3. 2026-06-27 21:22 UTCEG score recompute
  4. 2026-06-27 08:11 UTCEG score recompute
  5. 2026-06-26 19:56 UTCEG score recompute
  6. 2026-06-25 17:45 UTCEG score recompute
  7. 2026-06-18 02:22 UTCEG score recompute
  8. 2026-06-17 13:15 UTCEG score recompute
  9. 2026-06-16 23:39 UTCEG score recompute
  10. 2026-06-16 11:25 UTCEG score recompute
  11. 2026-06-15 23:11 UTCEG score recompute
  12. 2026-06-15 03:41 UTCEG score recompute
  13. 2026-06-14 23:18 UTCEPSS rescore
  14. 2026-06-14 15:27 UTCEG score recompute
  15. 2026-06-14 03:12 UTCEG score recompute
  16. 2026-06-13 23:00 UTCEPSS rescore
  17. 2026-06-13 14:54 UTCEG score recompute
  18. 2026-06-12 23:12 UTCEPSS rescore
  19. 2026-06-12 23:02 UTCEG score recompute
  20. 2026-06-12 10:47 UTCEG score recompute
  21. 2026-06-11 22:33 UTCEG score recompute
  22. 2026-06-11 10:19 UTCEG score recompute
  23. 2026-06-10 22:05 UTCEG score recompute
  24. 2026-06-10 09:50 UTCEG score recompute
  25. 2026-06-09 21:36 UTCEG score recompute
Show 18 more
  1. 2026-06-09 08:59 UTCEG score recompute
  2. 2026-06-08 20:44 UTCEG score recompute
  3. 2026-06-08 08:30 UTCEG score recompute
  4. 2026-06-07 20:17 UTCEG score recompute
  5. 2026-06-07 08:03 UTCEG score recompute
  6. 2026-06-06 19:49 UTCEG score recompute
  7. 2026-06-06 07:35 UTCEG score recompute
  8. 2026-06-05 19:21 UTCEG score recompute
  9. 2026-06-05 07:06 UTCEG score recompute
  10. 2026-06-04 18:53 UTCEG score recompute
  11. 2026-06-04 06:39 UTCEG score recompute
  12. 2026-06-03 18:25 UTCEG score recompute
  13. 2026-06-03 06:11 UTCEG score recompute
  14. 2026-06-02 17:57 UTCEG score recompute
  15. 2026-06-02 05:43 UTCEG score recompute
  16. 2026-06-01 17:29 UTCEG score recompute
  17. 2026-06-01 05:15 UTCEG score recompute
  18. 2026-05-24 06:17 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-45325?
CVE-2026-45325 is a high vulnerability published on May 18, 2026. @tmlmobilidade/utils has prototype pollution in its setValueAtPath Impact Prototype pollution vulnerability in @tmlmobilidade/utils for setValueAtPath(). Patches A fix is available in versions 20260509.0340.15 and up.
When was CVE-2026-45325 disclosed?
CVE-2026-45325 was first published in the National Vulnerability Database on May 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45325 actively exploited?
CVE-2026-45325 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-45325?
CVE-2026-45325 has a CVSS v4.0 base score of 8.2 (CNA self-assessment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-45325?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45325, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45325

Explore →

Is Your Infrastructure Affected by CVE-2026-45325?

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

Start Free Scan →Browse All CVEs