{"answers":{"affected":"3 open source packages ship an affected version, including skyvern.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-49619 exists.","fix":"No fix has been published for CVE-2025-49619 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-49619 is a high-severity code injection vulnerability in Skyvern, published on 7 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-49619 and fix it if it is affected.\n\nWhat it is: CVE-2025-49619 is a high-severity code injection vulnerability in Skyvern, published on 7 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-49619 exists.\n\nAffected packages and fixed versions:\n- skyvern (PyPI): affected all versions up to 0.2.0; no fix listed\n- skyvern (PyPI): affected all versions up to 0.2.0; no fix listed\n- skyvern (PyPI): affected all versions up to 0.2.0; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-49619/ (Markdown: https://insights.sbomify.com/CVE-2025-49619/index.md)","id":"CVE-2025-49619","markdown":"https://insights.sbomify.com/CVE-2025-49619/index.md","name":"CVE-2025-49619","record":{"aliases":["GHSA-h92g-3xc3-ww2r","PYSEC-2026-1929"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Skyvern automation platform","requires_auth":"low_privilege","summary":"Authenticated users can achieve remote code execution via server-side template injection in Skyvern workflow blocks.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-1336","name":"Improper Neutralization of Special Elements Used in a Template Engine"}],"description":"Skyvern through 0.1.85 is vulnerable to server-side template injection (SSTI) in the Prompt field of workflow blocks such as the Navigation v2 Block. Improper sanitization of Jinja2 template input allows authenticated users to inject crafted expressions that are evaluated on the server, leading to blind remote code execution (RCE).","ecosystems":["PyPI"],"exploits":{"exploitdb":1,"first_seen":"2025-06-07","github_poc":1,"max_poc_stars":3,"metasploit":1,"nuclei":0,"refs":[{"date":"2025-06-09T10:09:43Z","kind":"github_poc","ref":"https://github.com/cristibtz/CVE-2025-49619","stars":3,"title":"This script exploits CVE-2025-49619 in Skyvern to execute a reverse shell command."},{"date":"2025-06-07","kind":"metasploit","ref":"exploit/linux/http/skyvern_ssti_cve_2025_49619","stars":null,"title":"Skyvern SSTI Remote Code Execution"},{"date":"2025-06-15","kind":"exploitdb","ref":"52335","stars":null,"title":"Skyvern 0.1.85 - Remote Code Execution (RCE) via SSTI"}],"tier":"weaponised"},"has_fix":false,"headline":"Skyvern has a Jinja runtime leak","id":"CVE-2025-49619","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"code_injection","year":"2025"},"n_packages":3,"n_references":3,"next":{"headline":"Apache HTTP Server: mod_proxy_http2 denial of service","id":"CVE-2025-49630"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.2.0"],"package":"skyvern","purl":null,"source":"GHSA-h92g-3xc3-ww2r"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.2.0"],"package":"skyvern","purl":"pkg:pypi/skyvern","source":"GHSA-h92g-3xc3-ww2r"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.2.0"],"package":"skyvern","purl":"pkg:pypi/skyvern","source":"PYSEC-2026-1929"}],"prev":{"headline":"Information disclosure in Obsidian","id":"CVE-2025-49618"},"products":["Skyvern"],"published":"2025-06-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-17","vendors":["Skyvern"]},"summary":"Authenticated users can achieve remote code execution via server-side template injection in Skyvern workflow blocks.","url":"https://insights.sbomify.com/CVE-2025-49619/"}