CVE-2022-41713: deep-object-diff version 1.1.0 allows an external attacker to edit or add new properties to an object

Q: How do I fix CVE-2022-41713?

deep-object-diff: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Q: Is CVE-2022-41713 being exploited?

CVE-2022-41713 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-41713 affect?

CVE-2022-41713 affects deep-object-diff. Severity is medium (CVSS 5.3). deep-object-diff version 1.1.0 allows an external attacker to edit or add new properties to an object. This is possible because the application does not properly validate incoming JSON keys, thus allowing the '__proto__' property to be edit

Q: How urgent is CVE-2022-41713?

Priority 42/100. Public exploit reference; Remotely exploitable, no login, no user action

This week

MEDIUM 5.3REMOTEDOWNGRADE

CVE-2022-41713 is a medium-severity flaw (CVSS 5.3) affecting deep-object-diff. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

deep-object-diff version 1.1.0 allows an external attacker to edit or add new properties to an object. This is possible because the application does not properly validate incoming JSON keys, thus allowing the '__proto__' property to be edited.

Why this priority

Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.7% (top 46%)
CISA exploited list	No
Weakness	CWE-1321
Published	2022-11-03
Last modified	2026-06-17

Publisher (CNA): Fluid Attacks · Vendor: deep-object-diff project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-11-03 20:15 UTCPublished CVE record published
2026-06-17 05:03 UTCUpdated Record last modified

deep-object-diff project deep-object-diff DOWNGRADE

Affected: 1.1.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.1.0

1. Check installed version

npm ls deep-object-diff

2. No fixed release: DOWNGRADE to a release before 1.1.0

npm view deep-object-diff versions npm install deep-object-diff@"<1.1.0"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-41713?

deep-object-diff: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2022-41713 being exploited?

CVE-2022-41713 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-41713 affect?

CVE-2022-41713 affects deep-object-diff. Severity is medium (CVSS 5.3). deep-object-diff version 1.1.0 allows an external attacker to edit or add new properties to an object. This is possible because the application does not properly validate incoming JSON keys, thus allowing the '__proto__' property to be edit

How urgent is CVE-2022-41713?

Priority 42/100. Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs