Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

CVE-2024-45813 find-my-way

MEDIUMFix: delvedor/find-my-way@5e9e0eb

CVE-2024-45813 is a medium-severity (CVSS 5.3) CWE-1333 vulnerability in find-my-way. A fix is available for find-my-way — see the affected versions and patch details below.

ReDoS vulnerability in multiparametric routes in find-my-way

Also known asGHSA-rrr8-f88r-h8q6
Published
Sep 18, 2024
Updated
Aug 12, 2026
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Sep 20, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-45813.

EPSS Exploitation Probability

via FIRST.org ↗
0.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs51th percentile — riskier than 51% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2024-45813 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

219other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
find-my-waynpm
11.8Mdownloads / week

Description

find-my-way is a fast, open source HTTP router, internally using a Radix Tree (aka compact Prefix Tree), supports route params, wildcards, and it's framework independent. A bad regular expression is generated any time one has two parameters within a single segment, when adding a - at the end, like /:a-:b-. This may cause a denial of service in some instances. Users are advised to update to find-my-way v8.2.2 or v9.0.1. or subsequent versions. There are no known workarounds for this issue.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
📦npmfind-my-way5.5.0&&< 8.2.28.2.2npm install find-my-way@8.2.2
📦npmfind-my-way9.0.0&&< 9.0.19.0.1npm install find-my-way@9.0.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for find-my-way, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update find-my-way to 8.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-45813 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-45813 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2024-45813. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate
ProductFixed inAdvisory
multicluster engine for Kubernetes 2.6 for RHEL 8multicluster-engine/assisted-image-service-rhel8:v2.6.4-4RHSA-2024:11293
multicluster engine for Kubernetes 2.7 for RHEL 8multicluster-engine/assisted-service-8-rhel8:v2.7.2-1RHSA-2024:10857
Red Hat Advanced Cluster Management for Kubernetes 2.11 for RHEL 9rhacm2/acm-cluster-permission-rhel9:v2.11.4-4RHSA-2024:11381
Red Hat Advanced Cluster Management for Kubernetes 2.12 for RHEL 9rhacm2/acm-cli-rhel9:v2.12.1-4RHSA-2024:10865
Red Hat OpenShift Dev Spaces 3 Containersdevspaces/dashboard-rhel8:3.17-25RHSA-2024:10236

Frequently Asked Questions

find-my-way is a fast, open source HTTP router, internally using a Radix Tree (aka compact Prefix Tree), supports route params, wildcards, and it's framework independent. A bad regular expression is generated any time one has two parameters within a single segment, when adding a `-` at the end, like `/:a-:b-`. This may cause a denial of service in some instances. Users are advised to update to find-my-way v8.2.2 or v9.0.1. or subsequent versions. There are no known workarounds for this issue.
O3 Security · Impact-Aware SCA

Is CVE-2024-45813 in your dependencies?

O3 Security finds CVE-2024-45813 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2024-45813: find-my-way (Medium 5.3) | O3 Security