Skip to main content
VulnerabilityPublished Updated

CVE-2025-49619: Skyvern · Template Injection

Affects SkyvernSource CVE Database V5

0

Public exploit available (Metasploit, Exploit-DB) · 20% EPSS · CVSS 8.5 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
8.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
20.4% chance of exploitation in 30 days – higher than 97% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 7 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE published

    on cve.org

    , t = 0

  2. In Threat Radar

    record ingested

    , the same day as disclosure

  3. First Exploit-DB entry (opens in a new tab)

    Skyvern 0.1.85 - Remote Code Execution (RCE) via SSTI

    , 8 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Skyvern SkyvernAffected
  • =0
Fixed in–

AI-suggested

Given the absence of official patches, European organizations should implement the following specific mitigations: 1) Restrict network access to Skyvern instances, limiting exposure to trusted internal networks or VPNs to reduce attack surface. 2) Employ strict input validation and sanitization on any user-supplied data that interacts with the Jinja templates to minimize injection risks. 3) Enable detailed logging and monitoring around the sdk/workflow/models/block.py component to detect unusual template rendering or access patterns indicative of exploitation attempts. 4) Use application-layer firewalls or runtime application self-protection (RASP) tools that can detect and block suspicious template engine behaviors. 5) Isolate Skyvern environments using containerization or sandboxing to contain potential leaks. 6) Prepare for rapid patch deployment by tracking vendor updates closely and testing patches in staging environments before production rollout. 7) Conduct security reviews of workflows relying on Skyvern to identify and remediate any sensitive data exposure through templates.

Description

Skyvern through 0.1.85 has a Jinja runtime leak in sdk/workflow/models/block.py.

References

Community reviews

Loading reviews…