CVE-2023-26145

HIGHNVD 7.47.4—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.4 under NVD CVSS v3. EPSS exploit probability: 1.8%, top 17% 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
Elevated
7.4
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 3%CVSS: 7.4Exploit: NoneExposed: 0

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

This affects versions of the package pydash before 6.0.0. A number of pydash methods such as pydash.objects.invoke() and pydash.collections.invoke_map() accept dotted paths (Deep Path Strings) to target a nested Python object, relative to the original source object. These paths can be used to target internal class attributes and dict items, to retrieve, modify or invoke nested Python objects. Note: The pydash.objects.invoke() method is vulnerable to Command Injection when the following prerequisites are satisfied: 1) The source object (argument 1) is not a built-in object such as list/dict (otherwise, the __init__.__globals__ path is not accessible) 2) The attacker has control over argument 2 (the path string) and argument 3 (the argument to pass to the invoked method) The pydash.collections.invoke_map() method is also vulnerable, but is harder to exploit as the attacker does not have direct control over the argument to be passed to the invoked function.

CVSS v3
7.4
EG Score
7.4(medium)
EPSS
85.4%
KEV
Not listed

Published

September 28, 2023

Last Modified

November 21, 2024

References (6)

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
pydash0.0.0 ... v0.0.0 (118 versions)6.0.0—

Weakness Classification(3)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-26145?
CVE-2023-26145 is a high vulnerability published on September 28, 2023. This affects versions of the package pydash before 6.0.0. A number of pydash methods such as pydash.objects.invoke() and pydash.collections.invoke_map() accept dotted paths (Deep Path Strings) to target a nested Python object, relative to the original source object. These paths can be used to…
When was CVE-2023-26145 disclosed?
CVE-2023-26145 was first published in the National Vulnerability Database on September 28, 2023, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-26145 actively exploited?
CVE-2023-26145 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 85.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2023-26145?
CVE-2023-26145 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2023-26145?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-26145, 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-2023-26145

Explore →

Is Your Infrastructure Affected by CVE-2023-26145?

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

Start Free Scan →Browse All CVEs