Skip to main content
VulnerabilityPublished

CVE-2026-73647: quasarframework quasar · Prototype Pollution

Affects quasarframework quasarSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.6 Medium : upgrade to 2.22.0 when convenient.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 3.1 base score
5.6Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.22.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade quasar and quasarframework/quasar to 2.22.0.

Affected software

ProductAffectedFixed in
quasarframeworkquasarAffected
  • <2.22.0
Fixed in
  • 2.22.0
npmquasarframework/quasarpkg:npm/quasarframework/quasarOther threatsAffected
  • <2.22.0
Fixed in
  • 2.22.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Quasar Framework to version 2.22.0 or later, where this prototype pollution vulnerability is fixed. Applications should avoid passing user-controlled or partially user-controlled objects to the extend() function until upgraded.

Description

Quasar Framework is a framework for building high-performance Vue.js user interfaces. Prior to 2.22.0, the public extend() utility in ui/src/utils/extend/extend.js recursively copied attacker-controlled object keys during extend(true, target, source) deep merges without rejecting an own __proto__ property. The merge could descend into the prototype object and write attacker-controlled properties to Object.prototype in the same JavaScript process. Applications that passed user-controlled or partially user-controlled objects to extend() could experience logic bypass, unsafe default-option injection, denial of service, or other application-specific impact when polluted properties were later consumed. This issue is fixed in version 2.22.0.

References

Community reviews

Loading reviews…