CVE-2026-44292
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedprotobufjs compiles protobuf definitions into JavaScript (JS) functions. Prior to 7.5.6 and 8.0.2, protobufjs generated message constructors copied enumerable properties from a provided properties object without filtering the __proto__ key. If an application constructed a message from an attacker-controlled plain object, an own enumerable __proto__ property could alter the prototype of that individual message instance. This vulnerability is fixed in 7.5.6 and 8.0.2.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceprotobufjs copies enumerable properties from input objects to message constructors without filtering the __proto__ key. When applications construct messages from attacker-controlled objects, this allows prototype pollution of individual message instances, potentially enabling property injection or unexpected behavior.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 7.5.6>= 8.0.0, < 8.0.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify protobufjs versionRun 'npm list protobufjs' or inspect package.json/package-lock.json for the protobufjs entryAffected if Version is below 7.5.6 OR between 8.0.0 and 8.0.1 (inclusive)
-
Find protobufjs message constructor usageSearch codebase for patterns like 'new Message(...)' or 'Message.create(...)' where Message is a protobufjs generated classAffected if Code passes objects to message constructors from external or untrusted sources
-
Inspect input object handlingReview code paths that pass objects to protobufjs message constructors - check if the input originates from user input, HTTP requests, parsed JSON, or external APIsAffected if Input objects can be controlled by an attacker and are passed directly to message constructors without sanitization
-
Verify __proto__ filtering absenceSearch for sanitization logic that removes __proto__ or constructor keys before passing objects to protobufjs - look for Object.keys().filter(), delete operations, or custom sanitization functionsAffected if No sanitization removes __proto__ or constructor properties from objects before they reach protobufjs message constructors
You are affected if protobufjs version is vulnerable AND your application passes attacker-controlled objects to protobufjs message constructors without filtering __proto__ or constructor properties first.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped7.5.68.0.2
Upgrade protobufjs to version 7.5.6 or 8.0.2. Additionally, sanitize all input objects before passing them to protobufjs message constructors to remove any __proto__ or constructor properties.
protobufjs 7.5.6 (for 7.x users) or 8.0.2 (for 8.x users)
- 1. Identify the current version of protobufjs in your project by checking package.json or running `npm list protobufjs`
- 2. If using protobufjs version < 7.5.6, plan to upgrade to version 7.5.6
- 3. If using protobufjs version >= 8.0.0 and < 8.0.2, plan to upgrade to version 8.0.2
- 4. Run `npm install [email protected]` or `npm install [email protected]` (depending on your major version branch)
- 5. Run your test suite to verify the upgrade does not break existing functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,640.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44292 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-44292 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data