Bump path-to-regexp from 0.1.12 to 0.1.13 in /ui#485
Conversation
Bumps [path-to-regexp](https://github.com/pillarjs/path-to-regexp) from 0.1.12 to 0.1.13. - [Release notes](https://github.com/pillarjs/path-to-regexp/releases) - [Changelog](https://github.com/pillarjs/path-to-regexp/blob/v.0.1.13/History.md) - [Commits](pillarjs/path-to-regexp@v0.1.12...v.0.1.13) --- updated-dependencies: - dependency-name: path-to-regexp dependency-version: 0.1.13 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
JiwaniZakir
left a comment
There was a problem hiding this comment.
This bump addresses the ReDoS (Regular Expression Denial of Service) vulnerability in path-to-regexp 0.1.x (CVE-2024-45296), so the security motivation is sound. However, only ui/package-lock.json is modified here — ui/package.json is unchanged, which means the lockfile was likely updated via npm audit fix or manual editing rather than a direct version constraint change. It's worth verifying that package.json doesn't pin path-to-regexp to 0.1.12 explicitly or transitively through a dependency that locks it, otherwise this lockfile entry could be overwritten on the next npm install run by a different developer or CI environment. You can confirm the resolved version is stable by checking npm ls path-to-regexp output — if it's a transitive dependency (likely pulled in by express or a similar package), the correct fix is to add a lockfile override or overrides entry in package.json to ensure the patched version is enforced consistently.
Bumps path-to-regexp from 0.1.12 to 0.1.13.
Release notes
Sourced from path-to-regexp's releases.
Changelog
Sourced from path-to-regexp's changelog.
Commits
9fd0c870.1.13 (#425)7ccf02cfix: CVE-2026-4867Maintainer changes
This version was pushed to npm by ulisesgascon, a new releaser for path-to-regexp since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.