Skip to content
Server-Side Template Injection Vulnerability in DataGerry

Server-Side Template Injection Vulnerability in DataGerry

First seen 5 Nov 2026, 00:50 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 5, 2026 at 00:50 UTC
  • •CVE-2026-57853 affects DataGerry versions before 3.3.0.
  • •Authenticated attackers can exploit this vulnerability to execute arbitrary OS commands.
  • •A patch is available; immediate upgrade is recommended.

A severe server-side template injection vulnerability, CVE-2026-57853, has been identified in DataGerry versions prior to 3.3.0. This flaw allows authenticated attackers with 'base.docapi.template.add' permission to inject arbitrary Jinja2 payloads into the 'template_data' field via a POST request. When rendered through a GET request, the payload executes in a non-sandboxed environment, enabling attackers to run arbitrary OS commands as the DataGerry web process user, typically root in Docker deployments. The vulnerability was published on November 4, 2026, and has a CVSS score of 8.8, indicating a high severity. A patch has been released, and users are urged to upgrade to version 3.3.0 or later. There are currently no reports of public exploitation or proof-of-concept code. Security teams are advised to restrict permissions and monitor for suspicious activity.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Updated 12h ago How this analysis works

Timeline

2026-11-04
CVE-2026-57853 published
DataGerry disclosed a server-side template injection vulnerability affecting versions prior to 3.3.0.
Feedly
2026-11-04
Patch released
DataGerry released a patch for the vulnerability, urging users to upgrade to version 3.3.0 or later.
securityvulnerability.io

More articles in this cluster (5)

Following this threat?

Track DataGerry and CVE-2026-57853 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

Which versions are affected?
DataGerry versions prior to 3.3.0 are vulnerable.
Is there a patch available?
Yes, a patch has been released; users should upgrade to version 3.3.0 or later.
What actions should we take now?
Immediately upgrade DataGerry to version 3.3.0 or later and restrict permissions for template creation.