DeepPavlov up to 1.7.0 Config Reference Resolver params.py resolve code injection

Summaryinfo

A vulnerability, which was classified as critical, has been found in DeepPavlov up to 1.7.0. The affected element is the function resolve of the file deeppavlov/core/common/params.py of the component Config Reference Resolver. This manipulation causes code injection. This vulnerability appears as CVE-2026-112098. The attack may be initiated remotely. In addition, an exploit is available. The project was informed of the problem early through an issue report but has not responded yet.

Detailsinfo

A vulnerability has been found in DeepPavlov up to 1.7.0 and classified as critical. Affected by this vulnerability is the function resolve of the file deeppavlov/core/common/params.py of the component Config Reference Resolver. The manipulation with an unknown input leads to a code injection vulnerability. The CWE definition for the vulnerability is CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. As an impact it is known to affect confidentiality, integrity, and availability.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-112098. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1059 for this issue.

It is possible to download the exploit at github.com. It is declared as proof-of-concept. The project was informed of the problem early through an issue report but has not responded yet.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• DeepPavlov

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6
• 1.7.0

Website

• Product: https://github.com/deeppavlov/DeepPavlov/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Submitinfo

Accepted

• Submit #1012810: DeepPavlov up to 1.7.0 (commit 5f9fbed0c7191466bc7621e604b810f66f254c03, code still present in master) Code Injection (by Dem0000000)

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion