How severe is CVE-2022-36059?

CVE-2022-36059 has a CVSS score of 8.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-36059?

CVE-2022-36059 affects the following packages: matrix-js-sdk (npm). Ecosystems affected: npm.

How do I fix CVE-2022-36059?

Update matrix-js-sdk to 19.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-36059 is resolved across your whole dependency graph.

How do I detect CVE-2022-36059 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for matrix-js-sdk, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-36059 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2022-36059 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-36059 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-36059?

CVE-2022-36059 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 61th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-36059?

CVE-2022-36059 is classified as CWE-1321 (CWE-1321). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-36059 published, and has it been updated?

CVE-2022-36059 was published on March 28, 2023 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

HIGH severity

CVE-2022-36059 — matrix-js-sdk

HIGH

CVE-2022-36059 is a high-severity (CVSS 8.2) CWE-1321 vulnerability in matrix-js-sdk. A fix is available for matrix-js-sdk — see the affected versions and patch details below.

Prototype pollution in matrix-js-sdk

Also known asGHSA-rfv9-x7hh-xc32

Published

Mar 28, 2023

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-36059.

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs61th percentile — riskier than 61% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

167other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

matrix-js-sdknpm

431Kdownloads / week

Description

Impact

Events sent with special strings in key places can temporarily disrupt or impede the matrix-js-sdk from functioning properly, potentially impacting the consumer's ability to process data safely. Note that the matrix-js-sdk can appear to be operating normally but be excluding or corrupting runtime data presented to the consumer.

Patches

This is fixed in matrix-js-sdk 19.4.0.

Workarounds

Redacting applicable events, waiting for the sync processor to store data, and restarting the client can often fix it. Alternatively, redacting the applicable events and clearing all storage will often fix most perceived issues.

In some cases, no workarounds are possible.

References

https://learn.snyk.io/lessons/prototype-pollution/javascript/

For more information

If you have any questions or comments about this advisory please email us at security at matrix.org.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`matrix-js-sdk`	all versions	19.4.0`npm install matrix-js-sdk@19.4.0`

Affected Products

1 product · 1 configurations

Application

javascript sdkmatrix

< 19.4.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for matrix-js-sdk, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update matrix-js-sdk to 19.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-36059 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat Enterprise Linux 7	`thunderbird-0:102.3.0-3.el7_9`	RHSA-2022:6710
Red Hat Enterprise Linux 8	`thunderbird-0:102.3.0-3.el8_6`	RHSA-2022:6708
Red Hat Enterprise Linux 8.1 Update Services for SAP Solutions	`thunderbird-0:102.3.0-3.el8_1`	RHSA-2022:6716
Red Hat Enterprise Linux 8.2 Extended Update Support	`thunderbird-0:102.3.0-3.el8_2`	RHSA-2022:6715
Red Hat Enterprise Linux 8.4 Extended Update Support	`thunderbird-0:102.3.0-3.el8_4`	RHSA-2022:6713
Red Hat Enterprise Linux 9	`thunderbird-0:102.3.0-3.el9_0`	RHSA-2022:6717

Frequently Asked Questions

### Impact Events sent with special strings in key places can temporarily disrupt or impede the matrix-js-sdk from functioning properly, potentially impacting the consumer's ability to process data safely. Note that the matrix-js-sdk can appear to be operating normally but be excluding or corrupting runtime data presented to the consumer. ### Patches This is fixed in matrix-js-sdk 19.4.0. ### Workarounds Redacting applicable events, waiting for the sync processor to store data, and restarting the client can often fix it. Alternatively, redacting the applicable events and clearing all storage