maven-cve-full-resolver

Remediate Maven CVE vulnerabilities across research, strategy, and fix phases.

Updated Feb 28, 2026

Search Tags:#vulnerability #maven #pom.xml #cve #dependency #patch-management #dependency-tree

Ready to run

npx skills add https://github.com/sepehrrezaei/custom-agent-skills --skill maven-cve-full-resolver

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: maven-cve-full-resolver
Source: https://github.com/sepehrrezaei/custom-agent-skills/tree/main/maven-cve-full-resolver
Command: npx skills add https://github.com/sepehrrezaei/custom-agent-skills --skill maven-cve-full-resolver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end CVE remediation for Maven projects, guiding users through research, strategy selection, fix execution, and verification to remediate vulnerabilities efficiently.

Core Features & Use Cases

Parse CVEs from user input (CVE-YYYY-NNNNN, GHSA, scan outputs)
Research CVEs across sources (GitHub Advisories, NVD, OSV, Maven Central, Snyk) with a defined priority
Analyze Maven projects to identify affected dependencies via dependency tree and POM analysis
Propose multiple fix strategies and provide execution and verification steps
Gate user decisions to proceed with fixes and support multi-module projects
Phase-wise workflow with Research → Strategy → Fix & Verify

Quick Start

Determine the CVE you want to remediate and start the end-to-end remediation workflow.

Frequently Asked Questions about maven-cve-full-resolver

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

FAQPage Schema

How do I fix a CVE vulnerability in a Maven pom.xml dependency?▼

Fixing a Maven CVE vulnerability requires researching the advisory, analyzing your pom.xml dependency tree, selecting a remediation strategy, and applying version patches. This process guides you through each phase to resolve the vulnerable dependency.

How do I resolve vulnerable transitive dependencies in a multi-module Maven project?▼

Resolving vulnerable transitive dependencies in multi-module Maven projects involves analyzing the dependency tree to locate the inherited vulnerable package, then overriding the version in the parent or child pom.xml to apply a safe patch across modules.

What is the best way to research a CVE ID before patching a Java dependency?▼

Researching a CVE ID before patching involves checking multiple advisory sources like GitHub Advisories, NVD, OSV, Maven Central, and Snyk to understand the vulnerability impact and identify the safe patched version of the Java dependency.

Can I use a security scan report to remediate Maven vulnerabilities automatically?▼

Yes, you can parse CVE IDs directly from security scan outputs and reports to initiate the Maven vulnerability remediation workflow, which then researches the vulnerabilities and proposes structured fix strategies for your pom.xml.

Does this Maven CVE remediation workflow support multi-module projects?▼

Yes, the Maven CVE remediation workflow explicitly supports multi-module projects by analyzing the dependency tree and POM impact across modules, gating user decisions to proceed with fixes, and verifying the applied patches.