Update axios dependency (fixes GHSA-43fc-jf86-j433)#55
Merged
knolleary merged 1 commit intonode-red:masterfrom Feb 11, 2026
Merged
Update axios dependency (fixes GHSA-43fc-jf86-j433)#55knolleary merged 1 commit intonode-red:masterfrom
knolleary merged 1 commit intonode-red:masterfrom
Conversation
$ npm audit axios <=1.13.4 Severity: high Axios is Vulnerable to Denial of Service via __proto__ Key in mergeConfig - GHSA-43fc-jf86-j433 fix available via `npm audit fix --force` Will install axios@1.13.5, which is outside the stated dependency range node_modules/axios
hlovdal
added a commit
to hlovdal/hlovdal-node-red-lowercase-in-typescript
that referenced
this pull request
Feb 10, 2026
Upstream issue, node-red/node-red-admin#55. $ npm audit axios <=1.13.4 Severity: high Axios is Vulnerable to Denial of Service via __proto__ Key in mergeConfig - GHSA-43fc-jf86-j433 fix available via `npm audit fix --force` Will install node-red@4.0.9, which is a breaking change node_modules/axios node-red-admin 0.2.0 - 3.1.0 || >=4.0.2 Depends on vulnerable versions of axios node_modules/node-red-admin node-red 1.1.0-beta.1 - 2.2.3 || >=4.1.0-beta.1 Depends on vulnerable versions of node-red-admin node_modules/node-red 3 high severity vulnerabilities To address all issues (including breaking changes), run: npm audit fix --force $ npm ls axios @hlovdal/node-red-lowercase-in-typescript-cjs@1.0.0 /download/src/egne/hlovdal-node-red-lowercase-in-typescript ├─┬ node-red@4.1.4 │ └─┬ node-red-admin@4.1.2 │ └── axios@1.12.2 └─┬ wait-on@9.0.3 └── axios@1.13.5
Member
|
Thank you! Was just coming to do this - so appreciate the PR. |
hlovdal
added a commit
to hlovdal/hlovdal-node-red-lowercase-in-typescript
that referenced
this pull request
Feb 11, 2026
This reverts commit 212d704. Upstream fixed, node-red/node-red-admin#55.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed changes
Updating this package fixes security issue GHSA-43fc-jf86-j433/CVE-2026-25639.
From my reading of https://github.com/axios/axios/blob/v1.x/CHANGELOG.md and https://github.com/axios/axios/releases the main new feature of version 1.13 is support for HTTP2 and no breaking changes, so stepping up should not represent a problem.
Checklist
npm run testto verify the unit tests pass