cve-fix

Automate CVE remediation in Python dependencies via Jira, pipenv, and GitLab Merge Requests.

2|Updated Feb 16, 2026

Search Tags:#automation #security #vulnerability #dependency management #python #cve

One-click install

npx skills add https://github.com/dmzoneill/skills --skill cve-fix-dmzoneill

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: cve-fix
Source: https://github.com/dmzoneill/skills/tree/main
Command: npx skills add https://github.com/dmzoneill/skills --skill cve-fix-dmzoneill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jira_search, jira_view_issue, jira_assign, jira_transition, jira_add_comment, git_fetch, git_branch_list, git_branch_create, git_checkout, git_add, git_commit, git_push, gitlab_mr_list, gitlab_mr_create, podman_build, podman_run, memory_session_log, jira_attach_session, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of identifying and fixing CVE vulnerabilities in Python project dependencies, streamlining security updates.

Core Features & Use Cases

Automated CVE Discovery: Queries Jira for unresolved vulnerabilities affecting your project.
Dependency Updates: Updates Pipfile and Pipfile.lock with secure versions using pipenv.
Workflow Automation: Creates Merge Requests for fixes and updates Jira tickets accordingly.
Use Case: When a new critical CVE is announced for a Python library your project uses, this Skill can automatically find the fix, update your dependencies, and create a Merge Request for review.

Quick Start

Use the cve-fix skill to find and update dependencies vulnerable to CVE-2024-12345.

Frequently Asked Questions about cve-fix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate CVE remediation for Python dependencies in my project?▼

Automating CVE remediation involves querying Jira for unresolved vulnerabilities, updating Pipfile and Pipfile.lock via containerized pipenv, creating GitLab Merge Requests, and updating Jira tickets. This process requires precise CVE identification and package name normalization.

How does automated vulnerability remediation update Pipfile and Pipfile.lock?▼

Automated vulnerability remediation updates Pipfile and Pipfile.lock by running pipenv inside a containerized environment. This ensures dependency compatibility rules are met while applying secure package versions to resolve the identified CVE.

Can I use Jira and GitLab to automate security fixes for Python packages?▼

Yes, you can automate security fixes by integrating Jira and GitLab. The workflow queries Jira for vulnerability issues, updates Python dependencies, pushes the fix to a new Git branch, creates a GitLab Merge Request, and transitions the Jira ticket.

What is the best way to create a Merge Request for a Python dependency CVE fix?▼

The best way to create a Merge Request for a Python dependency CVE fix is to automate the workflow: fetch the vulnerable package from Jira, update the lockfile using pipenv, commit the changes to a new Git branch, and open a GitLab MR for review.

Do I need containerized pipenv to resolve Python dependency vulnerabilities?▼

Yes, containerized pipenv is required to resolve Python dependency vulnerabilities in this workflow. It builds and runs an isolated environment to safely update Pipfile and Pipfile.lock while adhering to dependency compatibility rules.

What are the limitations of automating CVE fixes for Python dependencies?▼

Limitations include the strict requirement for precise CVE identification and accurate package name normalization. Additionally, the workflow is tailored specifically for Python projects using Pipfile and Pipfile.lock, requiring Jira and GitLab integrations to function.