dbcve.org
Webaudiorecorder.jsApplication · Higuma

CVE-2026-2964

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability was identified in higuma web-audio-recorder-js 0.1/0.1.1. Impacted is the function extend in the library lib/WebAudioRecorder.js of the component Dynamic Config Handling. Such manipulation leads to improperly controlled modification of object prototype attributes. It is possible to launch the attack remotely. Attacks of this nature are highly complex. The exploitability is considered difficult. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

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 confidence

A prototype pollution vulnerability exists in the web-audio-recorder-js library where the extend function in lib/WebAudioRecorder.js improperly handles object merging during Dynamic Config Handling. This allows attackers to inject or modify Object.prototype properties by manipulating the configuration objects passed to the extend function, potentially leading to denial of service, code execution, or application behavior manipulation.

MitigationUpgrade to a patched version of web-audio-recorder-js that implements proper prototype chain validation in the extend function, or implement object property filtering (e.g., using Object.freeze on prototypes or validating input keys) before processing configuration data.

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
Webaudiorecorder.jsApplication
Affected:= 0.1= 0.1.1

CVSS 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify web-audio-recorder-js as a dependency
    Review your project's package.json, package-lock.json, or yarn.lock files for the web-audiorecorder-js or web-audio-recorder-js package dependency and note the installed version
    Affected if The package is listed with version 0.1 or 0.1.1
  2. Locate the library file
    Search your node_modules or src directory for lib/WebAudioRecorder.js from the web-audio-recorder-js library and open it for inspection
    Affected if The file exists in your codebase or node_modules
  3. Examine the extend function
    In lib/WebAudioRecorder.js, locate the extend function used for object merging and verify it lacks protections against __proto__, constructor, or prototype in the keys being merged
    Affected if The extend function performs shallow or deep object merging without filtering prototype-related properties
  4. Trace configuration input sources
    Search your codebase for calls to WebAudioRecorder or the extend function where configuration objects are passed; determine if any of these configuration objects or their properties originate from user input, URL parameters, API requests, or external data
    Affected if User-controlled or externally-sourced data is passed as configuration to the library without sanitization
  5. Verify prototype pollution impact
    If configuration is user-influenced, test by passing { "__proto__": { "testProp": "value" } } as part of the config and checking if Object.prototype.testProp becomes enumerable after the extend function executes
    Affected if Prototype properties can be injected and appear on Object.prototype

You are affected if you use web-audio-recorder-js version 0.1 or 0.1.1 AND pass untrusted or user-controlled configuration objects to the WebAudioRecorder without sanitizing prototype-related keys.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of web-audio-recorder-js that implements proper prototype chain validation in the extend function, or implement object property filtering (e.g., using Object.freeze on prototypes or validating input keys) before processing configuration data.

Fix this in Webaudiorecorder.js Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2964 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2964 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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