Update npm package protobufjs to v7.6.5 [SECURITY] - #409
Update npm package protobufjs to v7.6.5 [SECURITY]#409hash-dependencies[bot] wants to merge 1 commit into
protobufjs to v7.6.5 [SECURITY]#409Conversation
PR SummaryLow Risk Overview The lockfile is refreshed accordingly; there are no application source changes. Reviewed by Cursor Bugbot for commit 17f96fb. Bugbot is set up for automated code reviews on this repo. Configure here. |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 17f96fb. Configure here.
| "react-inspector": "^9.0.0", | ||
| "hono": "4.12.25", | ||
| "protobufjs": "7.6.4", | ||
| "protobufjs": "7.6.5", |
There was a problem hiding this comment.
Incomplete security override update
High Severity
The protobufjs override was bumped to 7.6.5, but package-lock.json still resolves @earendil-works/pi-coding-agent/node_modules/protobufjs to vulnerable 7.6.4. With npm ci in the Dockerfile, installs can fail as out-of-sync, or keep the unpatched package, so CVE-2026-59877 remains unfixed.
Reviewed by Cursor Bugbot for commit 17f96fb. Configure here.


This PR contains the following updates:
7.6.4→7.6.5protobufjs: Denial of Service via infinite loop in .proto option parsing
CVE-2026-59877 / GHSA-j3f2-48v5-ccww
More information
Details
Summary
protobufjs parsed option names by advancing through schema tokens until it reached an
=token, without checking for end of input. A crafted.protoschema that opens an option declaration but ends prematurely could cause the option parser to loop without ever terminating.This affects the reflection parsing path (
parse,Root.load,Root.loadSync).Impact
An attacker who can provide or influence
.protoschema text parsed by an application may be able to cause the parsing call to never return. Because Node.js is single-threaded, the blocked event loop prevents all other work in the process, resulting in a denial of service that persists until the process is externally terminated.Applications that only encode or decode protobuf binary data with trusted schemas are not directly affected.
Preconditions
.protoschema text influenced by an attacker.parse,Root.load, orRoot.loadSync.=assignment.Workarounds
Do not parse
.protoschemas from untrusted sources with affected versions. If untrusted schema text must be accepted, isolate parsing in a process or worker that can be safely terminated and bound it with a timeout, so a non-returning parse call cannot deny service to the rest of the application.Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
protobufjs/protobuf.js (protobufjs)
v7.6.5: protobufjs: v7.6.5Compare Source
Bug Fixes
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate.